We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This was originally discussed in jupyterlite/jupyterlite#287 (comment).
Where RetroLab doesn't handle the default welcome tour, but the notebook tour works out of the box.
Maybe this logic could be split so the tours are added in separate plugins?
jupyterlab-tour/src/defaults.tsx
Lines 487 to 495 in bc979d7
Or switch to using the settings-based way for defining tours for the defaults as well?
The plugin adding defaults could be disabled, and tours recreated manually.
The text was updated successfully, but these errors were encountered:
IStateDB
Those tours are more complicated as they interact with the UI. They cannot move to the settings.
I am not sure splitting them in multiple plugins is a good path as (I hope) the number of default tours will increase.
What about having a setting that select which default tours will be activated?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
This was originally discussed in jupyterlite/jupyterlite#287 (comment).
Where RetroLab doesn't handle the default welcome tour, but the notebook tour works out of the box.
Describe the solution you'd like
Maybe this logic could be split so the tours are added in separate plugins?
jupyterlab-tour/src/defaults.tsx
Lines 487 to 495 in bc979d7
Or switch to using the settings-based way for defining tours for the defaults as well?
Describe alternatives you've considered
The plugin adding defaults could be disabled, and tours recreated manually.
Additional context
The text was updated successfully, but these errors were encountered: