Fixing ESLint Prettier config #120
Closed
Conversation
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
ESLint seemed to be selectively not picking up .prettierconfig for its Prettier configuration, depending on its working directory. This should hopefully close the loop and eliminate disparities between local and CI environment checks.
Collaborator
Author
|
Closing for the moment, because that didn't solve the immediate issue in #119. I'm going to poke around some more at the root cause. |
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.
What does this PR do?
ESLint seemed to be selectively not picking up .prettierconfig for its Prettier configuration, depending on its working directory. This should hopefully close the loop and eliminate disparities between local and CI environment checks.