Front-end/Recipe runner/Composer

[jqnatividad]

qsv is designed to be easy to use, but IRL, "normal users" are intimidated by CLI interfaces.

The front-end/recipe runner will allow users to compose "recipes" that are not only composed of qsv commands, but other cli tools as well (e.g. jql, millr, csvkit, less, tee, ckanapi, other shell scripts, etc.).

• It will allow users to dynamically set qsv-relevant environment variables
• set logging dynamically and examine the qsv log file
• special handling of validation errors (i.e. the user can manually correct the .invalid.csv files and attempt validation again)
• browse/edit CSV files

Generated recipes can be run step-by-step from the front-end, and they can be saved and run from the command-line or integrated into any data pipeline.

[jqnatividad]

Something like https://github.com/YS-L/csvlens would be nice. Perhaps it can start as the view command.

[jqnatividad]

taking some inspiration from visidata as well (for composing/playing/saving recipes).

[jqnatividad]

This can be done as part of daemonizing qsv (#312 )

[github-actions[bot]]

Stale issue message

[github-actions[bot]]

Stale issue message

[jqnatividad]

Now looking to do this using Tauri and React, adopting an approach similar to this - https://www.highflux.io/blog/rust-tauri-react-developing-desktop-app-2022

[jqnatividad]

Now that luau is officially qsv's DSL, the front-end should also double as a qsv script development IDE with an integrated debugger.

[jqnatividad]

If https://github.com/YS-L/csvlens/issues/26 is implemented, we can just integrate with csvlens to do this.

[jqnatividad]

Closing as this will be done via #1006