Skip to content

build: stylelint not working correctly #20737

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 2 commits into from
Oct 8, 2020

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 6, 2020

Recently we changed the names of some Stylelint rules, but the linter wasn't updated which leads to several warnings for each file that goes through it.

For reference, Stylelint logs the following on the CI as well, but we didn't notice because it exits with a non-error code.

src/material/core/theming/tests/test-theming-api.scss
 1:1  ×  Unknown rule function-url-scheme-disallowed-list         function-url-scheme-disallowed-list
 1:1  ×  Unknown rule unit-allowed-list                           unit-allowed-list
 1:1  ×  Unknown rule declaration-property-value-disallowed-list  declaration-property-value-disallowed-list

src/material/core/theming/tests/test-theming-bundle.scss
 1:1  ×  Unknown rule function-url-scheme-disallowed-list         function-url-scheme-disallowed-list
 1:1  ×  Unknown rule unit-allowed-list                           unit-allowed-list
 1:1  ×  Unknown rule declaration-property-value-disallowed-list  declaration-property-value-disallowed-list

src/cdk/schematics/ng-update/test-cases/misc/global-stylesheets-test.scss
 1:1  ×  Unknown rule function-url-scheme-disallowed-list         function-url-scheme-disallowed-list
 1:1  ×  Unknown rule unit-allowed-list                           unit-allowed-list
 1:1  ×  Unknown rule declaration-property-value-disallowed-list  declaration-property-value-disallowed-list

Recently we changed the names of some Stylelint rules, but the linter wasn't updated
which leads to several warnings for each file that goes through it.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Oct 6, 2020
@crisbeto crisbeto requested a review from a team as a code owner October 6, 2020 15:46
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 6, 2020
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

We should also make this error exit with a non-zero code

@crisbeto
Copy link
Member Author

crisbeto commented Oct 6, 2020

I don't think we can do much about the exit code, it's just what Stylelint decided to exit with.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 6, 2020
@googlebot
Copy link

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla and removed cla: yes PR author has agreed to Google's Contributor License Agreement labels Oct 6, 2020
@josephperrott
Copy link
Member

@crisbeto played with it for a second and found how the way to set it to fail if these things are found. Pushed it up as a fixup.

@josephperrott josephperrott added cla: yes PR author has agreed to Google's Contributor License Agreement and removed cla: no PR author must sign Google's Contributor License Agreement: https://opensource.google.com/docs/cla labels Oct 6, 2020
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@crisbeto
Copy link
Member Author

crisbeto commented Oct 6, 2020

Nice! I don't know whether we handle fixup commits in this repo though.

@crisbeto crisbeto changed the title build: styleling not working correctly build: stylelint not working correctly Oct 6, 2020
@wagnermaciel wagnermaciel merged commit 6dfa28c into angular:master Oct 8, 2020
wagnermaciel pushed a commit that referenced this pull request Oct 8, 2020
* build: styleling not working correctly

Recently we changed the names of some Stylelint rules, but the linter wasn't updated
which leads to several warnings for each file that goes through it.

* fixup! build: styleling not working correctly

Co-authored-by: Joey Perrott <josephperrott@gmail.com>
(cherry picked from commit 6dfa28c)
@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 8, 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 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.

4 participants