Repository navigation
feat(cli): add validate command for model-level findings - #204
Conversation
Signed-off-by: Erik Nilsen <enilsen16@live.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PR SummaryLow Risk Overview A new Docs note Reviewed by Cursor Bugbot for commit b601ec7. Bugbot is set up for automated code reviews on this repo. Configure here. |
Problem
trogon-atlas apply --dry-runruns only the per-entity checks. The model-level rules (storyboard entries, projection order, field provenance) run only inValidateEventModel. The CLI has no command that calls it, so an author who uses only the CLI does not see these findings.Change
trogon-atlas validate <namespace>/<model>[@version]. It callsValidateEventModelfor the stored model. Without@version, it validates the latest version.--branchflag, so it validates the branch's view of the model.branch merge --dry-run.--format jsongivesevent_model,validation_summaryandvalidation.1when a finding is an error, and6when the model does not exist. A malformed address exits5before the CLI connects.Test
trogon-atlas-clientfor the address parser.1and reportsEVENT_NO_SWIMLANE(text and JSON). An empty model exits0. A model written only on a branch validates with--branchand exits6on baseline.cargo test -p trogon-atlas-cli,cargo test -p trogon-atlas-client, and clippy with-D warningson both crates pass.Closes #93
Need help on this PR? Tag
@codesmith-botwith what you need.