Repository navigation
Replies: 1 comment
|
Thanks, this was addressed by #10697, which added urlRouting: false in 1.76.0. With it set, navigation stays internal, so the host page's hash isn't read or changed. It removes the window.location.hash = originalHash cleanup I had in my overlay. Closing this as resolved. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Scalar's standalone API reference utilizes hash-based routing (
router: 'hash'). I tried all options and settled on hash. Since I'm using the Scalar UI API reference as an overlay within an already existing document, I have to perform several cleanups (e.g.,window.location.hash = originalHash). While this works, it isn't always reliable.I was wondering if it would be possible to introduce a 'none' option regardless of the side effects. For example, if I don't use the sidebar, I only need the initial view and the test request client (which opens yet another overlay). Alternatively, there could be an option for the test request to transform the initial view so that only one view is active at a time—essentially a 'single view' mode.
I believe the current UI was designed primarily to be used as a standalone view rather than contained within another document view. When using it in an overlay mode (such as a dialog or custom overlay), the UX could be slightly better with an alternate mode or something similar.
All reactions