Dirty cell flag
- Dominant language
- Python
- Stars
- 313
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure this is the right place, but I think it would make sense to add a dirty cell flag to indicate that the cell input has been changed after the cell was run, meaning that the output is not the result of the execution of the input.
JupyterLab will soon have a dirty cell visual indicator for that, but I think it should even be part of the Notebook format (see https://github.com/jupyterlab/jupyterlab/pull/10296#issuecomment-849627619).
Contributor guide
Research direction
Start by reviewing the proposed JupyterLab dirty-cell visual indicator and the linked JupyterLab pull request comment. Determine how a dirty-cell flag should be represented in the Notebook format and what format validation or compatibility requirements would define completion; this issue names no repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100