Rename accepted/0000-workspaces-link-phase-3.md to implemented/0000-workspaces-link-phase-3.md

arcanis · web-flow · commit b6772d6bc063 · 2017-07-12T12:39:41.000+01:00
diff --git a/implemented/0000-workspaces-link-phase-3.md b/implemented/0000-workspaces-link-phase-3.md
@@ -195,4 +195,4 @@ If workspaces don't make relative requires outside of their root (e.g. a file in
 
 * Combining multiple workspaces is out of scope of this document.
 
-* (related to general Workspaces RFC) How do we prevent people from publishing package and forgetting to setup correct dependencies for every workspace? E.g. `left-pad` may be absent from a workspace package.json and be present in the workspace root package.json. Testing the workspace code with node_modules installed in the root won't reveal this issue.
+* (related to general Workspaces RFC) How do we prevent people from publishing package and forgetting to setup correct dependencies for every workspace? E.g. `left-pad` may be absent from a workspace package.json and be present in the workspace root package.json. Testing the workspace code with node_modules installed in the root won't reveal this issue.

Original file line number	Diff line number	Diff line change
`@@ -195,4 +195,4 @@ If workspaces don't make relative requires outside of their root (e.g. a file in`
`195`	`195`
`196`	`196`	`* Combining multiple workspaces is out of scope of this document.`
`197`	`197`
`198`		-* (related to general Workspaces RFC) How do we prevent people from publishing package and forgetting to setup correct dependencies for every workspace? E.g. `left-pad` may be absent from a workspace package.json and be present in the workspace root package.json. Testing the workspace code with node_modules installed in the root won't reveal this issue.
	`198`	+* (related to general Workspaces RFC) How do we prevent people from publishing package and forgetting to setup correct dependencies for every workspace? E.g. `left-pad` may be absent from a workspace package.json and be present in the workspace root package.json. Testing the workspace code with node_modules installed in the root won't reveal this issue.