Update outdated information in the documentation
See original GitHub issueMuch of the Routing information suggests to use forRoot()
or forChild()
. However, in Singleton services you write:
since Angular 6.0, the best practice for providing services is with the
@Injectable()
providedIn
property as it makes your services tree-shakable.
The contradiction also applies to other Angular features, e.g. entryComponents
.
I propose to revise the documentation to not contradict itself and to provide updated information in all pages. Or, alternatively, to specify, e.g., why the Router is an exception to the rule.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:9
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Outdated Documentation | How It Can Cost You | by Jacquie ...
This article by Jacquie Samuels discusses how outdated documentation can cost your brand and your company.
Read more >The importance and challenges of up-to-date documentation -
By being updated, the documentation is getting rid of outdated information. This greatly reduces the risk of making mistakes, sending erroneous ...
Read more >8 Tips for Keeping Your Process Documentation Up to Date
If you don't have a plan to regularly update your process documentation, you probably have instructions that are inaccurate and outdated.
Read more >Outdated Documentation - Ubuntu Community Hub
The Ubuntu Community Installation Guide has not been updated since 2018. The Application guides since 2015. The vast majority of the hardware guide...
Read more >Creating and Updating Documentation - LinkedIn
The bane of every workplace with a set process seems to be keeping documentation updated. We recently realized that this is no different, ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we’ll move it to our consideration list.
You can find more details about the feature request process in our documentation.
@SetTrend I think you’re right in this case–I’ll talk to our infrastructure folks to see if we can adjust this.
I do have this issue on our list to review and prioritize.