Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change:
declaration-property-value-no-unknown: true
(see https://stylelint.io/migration-guide/to-15#added-declaration-property-value-no-unknown-rule)This prevents stylelint from screaming at us whenever we're doing a
pnpm update
in any of our projects related to the deprecated rules. However, as Stylelint itself writes in their migration guide: The rules were still working fine, they'll just be removed in v16.I decided to remove all deprecated rules alltogether since the error output looks like this before the actual stylelint-related issues are actually listed, which is significantly way more noise than I prefer:
WDYT @apfelbox @21christiansc