David Brochart
David Brochart
I'd say the end-user experience if the responsibility of the client. It could display a spinner showing that the directory content is being rendered, for instance.
Maybe we should wait and take advantage of the event system to implement that feature. I think it would be a good fit because in the case of huge directories,...
I didn't mean to use both APIs, but one or the other. It's already the case with the contents API in collaborative mode: JupyterLab doesn't use the REST API anymore...
> The event API will not provide you the initial directory listing, is it? Yes, we can decide that it provides the initial directory listing on client connection.
The event system could send initial content and changes of the whole directory tree (including sub-directories).
Thanks a lot @RobertRosca! I just changed the environment names, it was a bit confusing because we have a `lab` plugin which is common to the `jupyterlab` and `retrolab` plugins,...
Awesome, that works!
It looks like https://github.com/pypa/hatch/pull/484 has been merged and released. Looking forward to getting this PR in, but there is no rush @RobertRosca, whenever you find time :+1:
This looks great @RobertRosca, this will improve Jupyverse's workflow management so much! I just tried `hatch run dev.jupyterlab-noauth:jupyverse`, and got: ``` fps_uvicorn.cli:app: not found ```
Yes, it works fine now!