Repository navigation
Run and inspect project validation in project dev #1524
Description
Activity
I would just show each finding directly no grouping in that way would also fit to the LSP later on:
other actions:
- ignore error for a single file
- disable error entirely
- rerun
Soner (@shyim) Thanks for this -- so I'm clear, you would do this even if there are thousands of findings? In the earlier iteration, I'd included the filter overlay to manage scale -- but are you thinking that the "ignore/disable" function would be a way to manage that instead?
I'd spun up some notes about the ignore option last week post-refinement thinking it might be a "next step" after getting the report in place, but if it makes sense to ship it altogether then we can do it that way.
User story
As a developer, I want to run and inspect project validation from the
project devTUI experience, so I can understand code health and act on findings without piecing together CLI output.Scope
project dev.project validateflow.Acceptance criteria
project validateresult.Readiness checklist