Standardize dev tooling (ruff, CI, prettier, editorconfig) - #77
Merged
Conversation
Match the dev-tooling setup in vex-agent-integration. Ruff owns Python linting and formatting, prettier owns the frontend, and a CI workflow runs the test suites, lint, and format checks on every push and pull request. The backend job runs pytest against a throwaway Postgres. The suite builds its own schema on the fly, so there is no migration step. The frontend lockfile is now tracked so CI can install with npm ci.
Mechanical only. ruff format across the backend, plus safe autofixes (import sorting, datetime.UTC, unused-import removal). No behavior change.
Mechanical only. First prettier pass over the frontend sources.
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.
Closes #76
Brings the same dev tooling here that vex-agent-integration just adopted, so the two repos share one setup.
What is here
The frontend lockfile is now tracked so CI can install with npm ci.
Commits
The config and CI land first. The two bulk reformats (ruff format, prettier) are each their own commit and are listed in git-blame-ignore-revs so blame stays readable. The reformats are mechanical with no behavior change.
Verification
Ran the full flow locally against a disposable Postgres. All 252 backend tests pass, all 38 frontend tests pass, the production build compiles, and lint and format checks are clean.