-
Notifications
You must be signed in to change notification settings - Fork 12k
chore(blueprints): update codelyzer #2615
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
Conversation
Good stuff, thanks! |
A final change that I need to introduce as part of this PR are a few templete related rules. I will do that in a few hours today. |
This version includes template support and is compatible with the latest changes in the TemplateParser introduced by Angular 2.0.2. The following new rules are introduced: ``` // Does not allow access to private & protected // in inline templates "templates-use-public": true, // Makes sure `@Injectable()` is invoked and not // used as `@Injectable`. "invoke-injectable": true ``` There's one more rule which verifies if all members accessed in templates are defined in the component's controller but doesn't check the inheritance chain so I'll open a PR for it once we have the entire functionality implemented.
Ok, labelling it as WiP. Let me know when finished. |
@filipesilva it's ready, I only had to update |
This version includes template support and is compatible with the latest changes in the TemplateParser introduced by Angular 2.0.2. The following new rules are introduced: ``` // Does not allow access to private & protected // in inline templates "templates-use-public": true, // Makes sure `@Injectable()` is invoked and not // used as `@Injectable`. "invoke-injectable": true ``` There's one more rule which verifies if all members accessed in templates are defined in the component's controller but doesn't check the inheritance chain so I'll open a PR for it once we have the entire functionality implemented. Close angular#2615
This version includes template support and is compatible with the latest changes in the TemplateParser introduced by Angular 2.0.2. The following new rules are introduced: ``` // Does not allow access to private & protected // in inline templates "templates-use-public": true, // Makes sure `@Injectable()` is invoked and not // used as `@Injectable`. "invoke-injectable": true ``` There's one more rule which verifies if all members accessed in templates are defined in the component's controller but doesn't check the inheritance chain so I'll open a PR for it once we have the entire functionality implemented. Close #2615
This version includes template support and is compatible with the latest changes in the TemplateParser introduced by Angular 2.0.2. The following new rules are introduced: ``` // Does not allow access to private & protected // in inline templates "templates-use-public": true, // Makes sure `@Injectable()` is invoked and not // used as `@Injectable`. "invoke-injectable": true ``` There's one more rule which verifies if all members accessed in templates are defined in the component's controller but doesn't check the inheritance chain so I'll open a PR for it once we have the entire functionality implemented. Close angular#2615
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. |
This version includes template support and is compatible with the latest changes in the
TemplateParser
introduced by Angular 2.0.2.The following new rules are introduced:
There's one more rule which verifies if all members accessed in templates are defined in the component's controller but doesn't check the inheritance chain so I'll open a PR for it once we have the entire functionality implemented.