Repository navigation
style: establish a dprint formatting baseline - #14
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 dprint 0.57.1, pinned formatter plugins, format scripts, and a format-only CI job. Normalize the maintained petition-site/plugin source and documentation while preserving the existing Next ESLint configuration and rules. New max-lines enforcement is deferred to the next phase.
Keep module import/export order, JSX whitespace semantics, all product dependency declarations, every existing lock node, generated portraits/identity modules, migration snapshots, and media unchanged. Formatting tooling and the historical format baseline are separate commits.
Validation: npm ci --ignore-scripts; npm run format:check; existing npm run lint (zero errors, two existing Next image warnings); npm run build; plugin npm run check (typecheck/build and 3 tests); independent AST and full-field dependency review. No service launch or deployment.