honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Update link (#33166) 

Update multi-project workspace link

weblink on the angular.io website was not working, therefore, updated the multi-project workspace link.
PR Close #33166
This commit is contained in:
Harinder Singh 2019-10-15 14:41:58 +05:30 committed by Miško Hevery
parent 1cda80eb3a
commit 0bdb71c122
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
aio/content/guide/creating-libraries.md
View File

@ -19,7 +19,7 @@ Use the Angular CLI to generate a new library skeleton with the following comman
</code-example> </code-example>
<div class="alert is-helpful"> <div class="alert is-helpful">
<p>You can use the monorepo model to use the same workspace for multiple projects. See [Setting up for a multi-project workspace](guide/file-structure#multiple-projects).</p> <p>You can use the monorepo model to use the same workspace for multiple projects. See <a href="guide/file-structure#multiple-projects">Setting up for a multi-project workspace</a>.</p>
</div> </div>
This creates the `projects/my-lib` folder in your workspace, which contains a component and a service inside an NgModule. This creates the `projects/my-lib` folder in your workspace, which contains a component and a service inside an NgModule.
@ -213,4 +213,4 @@ This means that the TypeScript source can result in different JavaScript code in
For this reason, an app that depends on a library should only use TypeScript path mappings that point to the *built library*. For this reason, an app that depends on a library should only use TypeScript path mappings that point to the *built library*.
TypeScript path mappings should *not* point to the library source `.ts` files. TypeScript path mappings should *not* point to the library source `.ts` files.
</div> </div>