Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve interactive mode #30

Open
3 tasks
kasnerz opened this issue Jan 5, 2023 · 0 comments
Open
3 tasks

Improve interactive mode #30

kasnerz opened this issue Jan 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@kasnerz
Copy link
Owner

kasnerz commented Jan 5, 2023

Currently, only a very basic version of the interactive mode is implemented (#4). The user can enter edit mode, change cell value(s), and re-run the pipelines.

Only the edited cell ids are sent to the backend (together with the new values) & an altered version of the table is created for the current request. This way it should be relatively safe since the dataset will still contain the original, unmodified table.

TODO:

  • invalidate / hide pre-generated outputs
  • investigate if the current approach is safe enough
  • think about persistence - should we keep the edited values after a new table is fetched?
@kasnerz kasnerz added the enhancement New feature or request label Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant