Open
Conversation
bcb37
reviewed
Mar 18, 2026
Collaborator
bcb37
left a comment
bcb37
left a comment
There was a problem hiding this comment.
Odd: the npx command lints on pre-commit for me, but this yarn one doesn't
Collaborator
Author
|
so if you are on dev, and you make a change to both a frontend file and a backend file that the linter should catch, you don't encounter any issues? it detects both changes and autofixes them? |
Collaborator
Yeah, just tested it again. The yarn works but command doesn't error on an empty commit. |
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
2 participants
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.
noticed linter wasn't running on precommit