I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
Current behavior
There are many APIs that are deprecated long ago but not removed yet. For example, @angular/http and DeprecatedI18NPipesModule is deprecated as of v5. Or ViewEncapsulation.Native is deprecated as of v6.1. But there isn't a way to know things which is deprecated other than going to the page.
Expected behavior
I'd like to have a page which shows deprecated APIs so that developers can avoid using them.
Minimal reproduction of the problem with instructions
N/A
What is the motivation / use case for changing the behavior?
Environment
Angular version: X.Y.Z
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: XX
- Platform:
Others:
My mental image of what could this look like:
I'm submitting a...
Current behavior
There are many APIs that are deprecated long ago but not removed yet. For example,
@angular/httpandDeprecatedI18NPipesModuleis deprecated as of v5. OrViewEncapsulation.Nativeis deprecated as of v6.1. But there isn't a way to know things which is deprecated other than going to the page.Expected behavior
I'd like to have a page which shows deprecated APIs so that developers can avoid using them.
Minimal reproduction of the problem with instructions
N/A
What is the motivation / use case for changing the behavior?
Environment
My mental image of what could this look like:
