You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E.g. if you edit a dependency in a way that breaks a dependent cell (e.g. change a name), then revert, the dependent cell is still broken (because the link between dependent and dependency is lost when the dependency is broken).
Ideally dependents would always be up-to-date with their dependencies, and sometimes the dependencies need to be dynamically discovered. E.g. if a cell uses an undefined name (and fails) then another cell defines it, the first cell should be re-run.
This doesn't really fit Vite's dependency model so it might be hard to accomplish. But maybe we want our own dependency tracking in order to support runtime state dependencies in addition to code dependencies.
The text was updated successfully, but these errors were encountered:
E.g. if you edit a dependency in a way that breaks a dependent cell (e.g. change a name), then revert, the dependent cell is still broken (because the link between dependent and dependency is lost when the dependency is broken).
Ideally dependents would always be up-to-date with their dependencies, and sometimes the dependencies need to be dynamically discovered. E.g. if a cell uses an undefined name (and fails) then another cell defines it, the first cell should be re-run.
This doesn't really fit Vite's dependency model so it might be hard to accomplish. But maybe we want our own dependency tracking in order to support runtime state dependencies in addition to code dependencies.
The text was updated successfully, but these errors were encountered: