This repository was archived by the owner on Dec 27, 2025. It is now read-only.
Add fmt, lint, and check commands for scenario files #1
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
probitas fmtcommand that runsdeno fmt --no-configon scenario filesprobitas lintcommand that runsdeno lint --no-configon scenario filesprobitas checkcommand that runsdeno check --no-configon scenario files_deno.tsmodule for common Deno subcommand execution logicWhy
Scenario files need formatting, linting, and type-checking just like any TypeScript code, but should use the same file discovery logic as
probitas run. These commands bridge Deno's tooling with Probitas' configuration-driven file discovery, allowing users to run standard Deno tooling without manually specifying files.All three commands use
--no-configto avoid conflicts with project deno.json, and lint excludes rules incompatible with scenario imports (no-import-prefix, no-unversioned-import).Test Plan
probitas fmt --helpand verify help text displays correctlyprobitas lint --helpand verify help text displays correctlyprobitas check --helpand verify help text displays correctly