Allow users to edit the current cache

[abhi18av]

This feature request is regarding the ability to make edits to the current database which is loaded.

Use-case:

1. Often, when conducting the analysis, one needs to resume the pipeline to reuse the work previously done. However, this process is not full-proof and it'd be nice to be able to change the individual location of the cache for time-taking processes which completed but were marked as failed due to some

2. Another use-case is for processes which fail and, after a bit of tweaking the .command.sh file they work successfully - instead of marking those as failed, it makes sense to mark them as succeeded. NOTE: This might clash with the overall idea of computing cache on the fly based on the script content.

[jagedn]

this is an interesting idea

I'm thinking to provide some --dev parameter to allow the edition of specific fields. When present the UI will provide some inputs fields or buttons

[abhi18av]

Hmm, good point.

But perhaps this approach might not scale if people want to open multiple caches at the same time 🤔

What if there's a toggle in the UI to enable/disable editing of a cache. This way, we can even display on the UI which cache has been modified and which is still in original state.

========

But before, that let's standardize the terminology (feel free to suggest changes) -

1. Cache - collection of nextflow execution metadata - but this folder has other information such as assets etc

2. Execution cache - this cache is unique for every execution of pipeline

Single Nextflow cache -> Multiple execution cache(s)

What do you think?