feat(fix): multi-language check resolution — Cargo/Python auto-detect + openswarm.json checks config#193
Merged
Merged
Conversation
… + openswarm.json checks config (INT-2303) openswarm fix only understood package.json scripts, so Rust/Python projects always died with 'No checks resolved'. Check resolution is now ecosystem-aware, first non-empty source wins: - openswarm.json "checks" (key -> shell command, run via sh -c): the explicit escape hatch for any language/toolchain and for mixed repos - package.json scripts (unchanged npm path) - Cargo.toml: cargo check --all-targets + cargo test by default; clippy/build resolve when requested via --checks - Python markers (pyproject/setup.py/setup.cfg/requirements.txt): ruff check . / mypy . / pytest, each gated on the repo actually being configured for the tool; --checks bypasses the gating Check gains a display field so prompts show 'pytest -x' instead of the sh -c wrapper. RepoMetadataSchema accepts the new checks map. Verified: 35 unit tests (resolveProjectChecks priority/gating/aliases, cargo+pytest output parsing, schema round-trip) + E2E smoke on real cargo/pytest fixtures incl. openswarm.json override and red-check file blame. Full suite 1326 passed, lint 0, tsc clean.
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.
Summary
openswarm fixonly understoodpackage.jsonscripts — Rust/Python projects always exited withNo checks resolved(INT-2303). Check resolution is now ecosystem-aware; the first non-empty source wins:openswarm.json"checks"—{"key": "shell command"}, run viash -c. The explicit escape hatch for any language/toolchain and for mixed repos.package.jsonscripts — unchanged npm path.Cargo.toml—cargo check --all-targets+cargo testby default;clippy/buildresolve when requested via--checks lint,build.ruff check ./mypy ./pytest, each included only when the repo is actually configured for the tool;--checksbypasses the gating.Checkgains adisplayfield so worker prompts showpytest -xinstead of thesh -cwrapper.RepoMetadataSchemaaccepts the newchecksmap.Verification
resolveProjectCheckspriority/gating/aliases, cargo+pytest output parsing,openswarm.jsonschema round-tripcargo newcrate (autocheck+test, green), pytest project (autopytest, green),openswarm.jsonchecks override, red check → correct file blame from pytest output🤖 Generated with Claude Code