chore: format code to project rules#155
Open
danyill wants to merge 1 commit into
Open
Conversation
Run the project formatter (eslint --fix + prettier --write) to fix the 45 files flagged by `npm run lint`. Formatting-only; no behavioural changes. Closes openscd#150
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.
Runs the project formatter (
eslint --fix+prettier --write) to fix the 45 files flagged bynpm run lint. Formatting-only — no behavioural changes.npm run lintnow passes clean.Closes #150
Relationship to #153 (vitest)
These 45 files overlap heavily with #153 (both touch the same
.spec.tsfiles), but the changes are conflict-free: #153 only rewrites theimport … from "chai"→"vitest"line, while prettier reformats other lines.git merge-treemerges #150 and #153 cleanly (no conflicts), so they can be merged in either order.