Skip to content

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

Closed
wants to merge 1 commit into from
Closed

chore(blueprints): update codelyzer #2615

wants to merge 1 commit into from

Conversation

mgechev
Copy link
Member

@mgechev mgechev commented Oct 9, 2016

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.

@filipesilva
Copy link
Contributor

Good stuff, thanks!

@mgechev
Copy link
Member Author

mgechev commented Oct 10, 2016

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.
@filipesilva
Copy link
Contributor

Ok, labelling it as WiP. Let me know when finished.

@mgechev
Copy link
Member Author

mgechev commented Oct 10, 2016

@filipesilva it's ready, I only had to update tslint.json.

@mgechev mgechev deleted the codelyzer-templates branch October 10, 2016 22:12
JJayet pushed a commit to JJayet/angular-cli that referenced this pull request Oct 14, 2016
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
Brocco pushed a commit that referenced this pull request Oct 19, 2016
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
texel pushed a commit to splice/angular-cli that referenced this pull request Nov 3, 2016
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
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants