-
Notifications
You must be signed in to change notification settings - Fork 42
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
[WIP] aksel stylelint #1973
[WIP] aksel stylelint #1973
Conversation
🦋 Changeset detectedLatest commit: b2a0971 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
something is up with stylelint plugin definition, was hoping we could wrap all our rules in one nice plugin, but it might have to become a large list of rules in the main package.json (under "stylelint" section) |
9900fae1f | 45 komponenter | 266 stories |
Its alive! 🧟 |
Hvordan skiller dette seg fra plugins som stylelint-value-no-unknown-custom-properties ? |
Hei, den regelen gir en del overlap og er mer generisk i de tilfeller man bare refererer til en token som ikke finnes i det hele tatt, men den kan I de tilfeller for tokens man definerer og bruker en token selv sjekke om du har en skrivefeil eller av en eller annen grunn refererer til en design system token som ikke finnes (selv om selve tokenen finnes). Dette skjer med feks override + bruk (skjermbilde under). I tillegg til referanser, så sjekker den navn av tokens når man overrider (re-definerer) en token. /*...*/
--a-illegal-token: 5px;
/*...*/ |
Need to test manual upload to NPM (and dload + use). before merge:
|
this commit is a good "base" for developing future stylelint rules
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚢 🇮🇹
#1899