Repository navigation
Angular 4, deprecated code not summarized #15556
Description
I'm submitting a ... (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
So I am maintaining 4 very large projects in Angular.
There is no way for me to know, when I open each project, which code has been deprecated.
The only reported issue I see is when I run AOT, a message of <template> now needing to be <ng-template>
However, there are no mentions of any issues with things like Renderer now needing to ne Renderer2.
Expected behavior
I expect TypeScript and / or cli to report a summary of all deprecated API so we can fix'em before ng5 is out.
@angular/cli: 1.0.0
node: 6.9.5
os: win32 x64
@angular/animations: 4.0.0
@angular/common: 4.0.0
@angular/compiler: 4.0.0
@angular/core: 4.0.0
@angular/forms: 4.0.0
@angular/http: 4.0.0
@angular/platform-browser: 4.0.0
@angular/platform-browser-dynamic: 4.0.0
@angular/router: 4.0.0
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.0
@angular/language-service: 4.0.0
@ngtools/webpack: 1.3.0
Not sure if this issue should be opened against cli repo.
FYI, in WebStorm I will see cross outs on deprecated API, but again, I am dealing with thousands of files so I can't open each one and look for cross outs, see below:
Angular 2 Kitchen sink: http://ng2.javascriptninja.io
and source@ https://github.com/born2net/Angular-kitchen-sink
Regards,
Sean
Activity
DzmitryShylovich commentedon Mar 28, 2017
this is angular repo :)
born2net commentedon Mar 28, 2017
well it's up to Angular (or cli I am not sure) to report the issue, not related to TypeScript. But would be nice if it displayed in the TypeScript console same as Angular does with language service.
wKoza commentedon Mar 28, 2017
With Webstorm :
Code | Run Inspection by Name... -- search for "deprecated" ...
born2net commentedon Mar 28, 2017
that's AWESOME!!! tx
Now I still think this issue should be resolved so I will keep open, but this sure helps!!!
tx
Sean
born2net commentedon Mar 28, 2017
Toxicable commentedon Mar 28, 2017
This isn't an Issue with the Angular framework. If you want reports you need you development tools to report it Angular dosen't do this itself with it's current depreciation method. If anything, this should be in the CLI imo
born2net commentedon Mar 28, 2017
I can move to cli sure, let's see what some of the ng dev think, and if need be will move sure,
tx!
IgorMinar commentedon Mar 29, 2017
@mgechev and @alexeagle have some tslint checks in works that surface all the deprecation automatically while linting.
mgechev commentedon Mar 29, 2017
There's a rule for automatic migration of
<template>...</template>to<ng-template>...</ng-template>in the codelyzer's repo.Waiting for this PR to be merged in order to allow auto-fixes in external templates.
born2net commentedon Mar 29, 2017
also renderer now renderer2 etc..
alexeagle commentedon Mar 29, 2017
Deprecation linter is here: palantir/tslint#2395
8 remaining items
jenniferfell commentedon May 10, 2019
Removed feature and fix labels, to put this back into triage queue for re-triage in context of latest release.
pkozlowski-opensource commentedon Mar 13, 2020
Duplicate of #11996
angular-automatic-lock-bot commentedon Apr 13, 2020
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.