Skip to content
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

build: add linting for classList usage #17388

Merged
merged 1 commit into from
Oct 14, 2019

Conversation

crisbeto
Copy link
Member

Once in a while we hit an issue because we use some of the classList methods in a way that isn't supported in all browsers (e.g. passing multiple parameters to add in #17378). These changes add a simple lint rule to catch these cases earlier.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Oct 13, 2019
@crisbeto crisbeto requested review from jelbourn and a team as code owners October 13, 2019 12:12
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 13, 2019
@crisbeto crisbeto force-pushed the classlist-signature-linting branch 2 times, most recently from 721ad03 to d71b933 Compare October 13, 2019 12:17
Once in a while we hit an issue because we use some of the `classList` methods in a way that isn't supported in all browsers (e.g. passing multiple parameters to `add` in angular#17378). These changes add a simple lint rule to catch these cases earlier.
// For each of the variant selectors that is present in the button's host
// attributes, add the correct corresponding MDC classes.
for (const pair of HOST_SELECTOR_MDC_CLASS_PAIR) {
if (this._hasHostAttributes(pair.selector)) {
(elementRef.nativeElement as HTMLElement).classList.add(...pair.mdcClasses);
Copy link
Member Author

Choose a reason for hiding this comment

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

Looks like we had one of these already that we hadn't noticed.

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. Good use on the type checker to ensure we don't incorrectly add failures for similarly named methods.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 14, 2019
@mmalerba mmalerba merged commit 1cc3a79 into angular:master Oct 14, 2019
@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 Nov 14, 2019
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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants