Skip to content

build: update tslint rules to remove usage of whitelist in comments #20618

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

Merged
merged 1 commit into from
Sep 22, 2020

Conversation

josephperrott
Copy link
Member

Remove usage of the term whitelist in commenting for validateDecoratorsRule

Remove usage of the term whitelist in commenting for validateDecoratorsRule
@josephperrott josephperrott added action: merge The PR is ready for merge by the caretaker merge safe target: patch This PR is targeted for the next patch release area: build & ci Related the build and CI infrastructure of the project labels Sep 21, 2020
@josephperrott josephperrott requested a review from a team as a code owner September 21, 2020 16:56
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 21, 2020
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Not feeling strongly about the nit comment 😄

Comment on lines +8 to +9
* Properties can be forbidden by prefixing their name with a `!`. Supports specifying a matcher for
* filtering valid files via the third argument, as well as validating all the arguments by passing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Properties can be forbidden by prefixing their name with a `!`. Supports specifying a matcher for
* filtering valid files via the third argument, as well as validating all the arguments by passing
* Properties can be forbidden by prefixing their name with a `!`. Supports an allow list for
* filtering valid files via the third argument, as well as validating all the arguments by passing

Just an optional nit comment for it being more accurate. A matcher (subjectively) implies a function/predicate to me.

@annieyw annieyw merged commit 09e7779 into angular:master Sep 22, 2020
annieyw pushed a commit that referenced this pull request Sep 22, 2020
…20618)

Remove usage of the term whitelist in commenting for validateDecoratorsRule

(cherry picked from commit 09e7779)
@josephperrott josephperrott deleted the tslint-fix branch September 28, 2020 18:23
@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 Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants