Update markdownlint and stylelint to the latest#96
Open
yokuze wants to merge 4 commits intosilvermine:masterfrom
Open
Update markdownlint and stylelint to the latest#96yokuze wants to merge 4 commits intosilvermine:masterfrom
yokuze wants to merge 4 commits intosilvermine:masterfrom
Conversation
This lets us use the new gitignore option so we do not need as many exclude globs
After updating, nesting-selector-no-missing-scoping-root started reporting violations for SCSS @Mixins. We allow `&` without a clear root in mixins because those types of operations are part of what mixins are for.
60ce14f to
2dfd281
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With this update to markdownlint, the
gitignoresetting now works as expected, which is helpful for local gitignore AI-related markdown files.This also formats package.json to 3 space indentation, and reorders some PRD dependencies that got out of the order that package.json uses when running
npm i.