Skip to content

Upgrade stylelint config#753

Merged
simurai merged 4 commits intorelease-12.2.3from
upgrade-stylelint-config
Apr 16, 2019
Merged

Upgrade stylelint config#753
simurai merged 4 commits intorelease-12.2.3from
upgrade-stylelint-config

Conversation

@shawnbot
Copy link
Contributor

This PR is a placeholder for upgrading to stylelint-config-primer@6.0.0 once primer/stylelint-config#27 is ready. For now, let's see if the canary release of primer/stylelint-config#25 plays nicely.

@shawnbot
Copy link
Contributor Author

Oof, well this was kind of tricky. My assumption in primer/stylelint-config#25 was that even with @primer/css as a peer dependency, it (Node) would still be able to resolve everything when run within that package. This was a bad assumption, so what I ended up doing was disabling both the primer/selector-no-utility and selector/no-override rules in this repo's stylelint config.

The result is that we still get all of the syntax and formatting rules, but we don't enforce "duplicate" selectors or classnames here because this is the source of those values.

@shawnbot shawnbot force-pushed the upgrade-stylelint-config branch from 4dd51b6 to 34cef02 Compare April 11, 2019 18:32
@shawnbot shawnbot force-pushed the upgrade-stylelint-config branch from 34cef02 to 3ad45c5 Compare April 11, 2019 18:41
@shawnbot shawnbot marked this pull request as ready for review April 11, 2019 19:03
Copy link
Contributor

@simurai simurai left a comment

Choose a reason for hiding this comment

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

Looks good to me. 😝

I assume we need to add these rules to .stylelintrc.json because primer/css should be the only exception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants