Repository navigation
chore: add prettier config and normalize frontend formatting - #69
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add .prettierrc (printWidth 100, double quotes, LF) inferred from the repo's de-facto style, plus .prettierignore (node_modules/dist/coverage/.gga/openspec).
Normalize the 51 frontend files that previously failed
prettier --check. Pure formatting — no behavioral change. After this,npx prettier --check .passes repo-wide (enforceable gate).Config choice minimizes churn: code already lived at ~100 columns (424 lines >80 but only 113 >100) and uses double quotes (332 vs 0 single), so printWidth 100 + singleQuote false match authoring.