`dataflow library`, point to a directory of notebooks
asg017 opened this issue · comments
Right now dataflow only runs a single .ojs file, like dataflow run notebook.ojs. this is fairly limiting, if you're working on multiple notebooks at a time, you'd either have to keep killing/restarting dataflow to point to a different file, or run them separately on different ports (which isn't fun at all).
dataflow library (different name?) could instead point to a directory of .ojs files. The dev server would then 1) allow you to view any of the .ojs files in that directory, and 2) offer a UI for navigating through all the notebooks.
This would be similar to jupyterlab, which has a navigation UI for a given directory (and even displays non-notebook files).
- Most of the dev server logic assumes the same
notebookPath, so will need to probably rewrite most of it - Detect when notebooks are added/removed
- What should the navigation UI look like, and how to distinguish it from notebook contents
imho the cleanest option would be to still start from a file, but serve an entire directory and simply allow navigating to /other/notebook.ojs from links rendered from markdown or otherwise in a regular cell. This way we can experiment with navigation live :) and avoid baking something into the UI