You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2024. It is now read-only.
I decided against using the ES6++ syntax (@Inject annotations and type annotations) because of the poor linting support. For anyone who follows in my footsteps, here's the latest on the linter front at the time of writing: https://groups.google.com/d/msg/angular-dev/JdQHLzAA9xg/TcfpVCeEGGEJ
There is some discussion about ES6 support for ESLint here, although ES6++ has not been discussed: eslint/eslint#1291
There is an issue against JSHint specifically for ES6++ support: jshint/jshint#1789
I think a note about linter support belongs as a FAQ in the docs: "Should I use the ES6++ syntax in production?". The answer is probably no because you'll most likely lose the ability to lint.
I decided against using the ES6++ syntax (
@Injectannotations and type annotations) because of the poor linting support. For anyone who follows in my footsteps, here's the latest on the linter front at the time of writing: https://groups.google.com/d/msg/angular-dev/JdQHLzAA9xg/TcfpVCeEGGEJThere is some discussion about ES6 support for ESLint here, although ES6++ has not been discussed: eslint/eslint#1291
There is an issue against JSHint specifically for ES6++ support: jshint/jshint#1789
I think a note about linter support belongs as a FAQ in the docs: "Should I use the ES6++ syntax in production?". The answer is probably no because you'll most likely lose the ability to lint.