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
The latest version is now using the api/configendpoint from Jupyter Server to store the tours seen independently of the workspaces.
From the demo 1258 you are linking I see the tours are working. I guess the fix should be on Lite to implement the handling of the standard config REST endpoint.
JupyterLite does not implement all the Jupyter Server endpoints (for example there is no api/terminals or api/me) Up until now api/config has not been needed. So I was wondering if there could be way to get away without having to implement it, just like it was the case with the previous version of jupyterlab-tour.
store the tours seen independently of the workspaces.
Description
As noticed in jupyterlite/jupyterlite#1258 (comment) and #76 (comment), the new JupyterLab 4 compatible version does not seem to work
Reproduce
For example testing with ReadTheDocs preview for jupyterlite/jupyterlite#1258: https://jupyterlite--1258.org.readthedocs.build/en/1258/_static/lab/index.html
Expected behavior
jupyterlab-tour
was running fine with JupyterLite before.Looks like this might be related to some new server side logic introduced recently in #81? Could this be made optional to keep JupyterLite support?
The text was updated successfully, but these errors were encountered: