-
Notifications
You must be signed in to change notification settings - Fork 6.8k
chore: cleanup schematics #12266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: cleanup schematics #12266
Conversation
devversion
commented
Jul 18, 2018
- Add licenses to all source files for the schematics & update-tool
- Enables linting for schematics folder (except template files; and utils taken verbatim from devkit)
- Fixes wrong file extension for tests inside of schematics
- Fixes IDE warnings in schematics folder (related: https://youtrack.jetbrains.com/issue/WEB-33060)
* Use of this source code is governed by an MIT-style license that can be | ||
* found in the LICENSE file at https://angular.io/license | ||
*/ | ||
/* tslint:disable */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why are we removing the license on these files if we added it everywhere else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I accidentally removed them. Re-added and also uses Google LLC
instead of Google Inc.
@devversion looks like there is a lint error |
* Add licenses to all source files for the schematics & update-tool * Enables linting for schematics folder (except template files; and utils taken verbatim from devkit) * Fixes wrong file extension for tests inside of schematics * Fixes IDE warnings in schematics folder (related: https://youtrack.jetbrains.com/issue/WEB-33060)
93f1f8e
to
12cf39d
Compare
@josephperrott Fixed (happened because of the new tree schematic that has been merged) |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |