search

tnunnink / AutoSpex

A Windows application that runs configurable specifications against a source L5X file to validate the project content.
MIT License
2 stars 0 forks source link

Persist Runs On Completion #40

Closed tnunnink closed 3 weeks ago

tnunnink commented 1 month ago

I think the route I want to go is to persist each run to keep a history of runs the user can look back on. To manage storage, we can only keep the last 100 or so and this can be configurable in settings. User can also clear history or delete specific runs.

This makes each run essentially read only. When running again, each time it produces a new result and posts to the database.

Since suppression are configured, there is no mutable state in the run we care about.

I think this will make #32 moot. Maybe having it on collection, and source? Not sure about spec though. Spec Run command should then maybe just execute the local runner.

tnunnink commented 1 month ago

With the removal of variables, there is only one tab for each node (specs/criteria). It seems like I should just get rid of tabs then. There is no point in having 1/2 tabs. #32 would go away then, and I would just have a history page to view and filter runs. I think this simplifies the UI. Less things to care about. Less ways to do things.