-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
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
Front-end Library Routing refactor #11614
Conversation
24673d9
to
3fc8026
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll try to explore fixing up this routing without using # urls.
apply wildcard in buildapp.py
Sorry @dannon, you were right. I've read a bit here and there, and figured it out. I probably shouldn't have argued about it and just done it right away. I hope it looks better now. Thanks a lot for checking it! |
@OlegZharkov No worries about a little bit of discussion man :) This looks like exactly what I was thinking of -- I'm really glad you jumped on it and knocked it before I could even follow up this evening! |
This PR was merged without a "kind/" label, please correct. |
can someone also add |
done |
depends on #11485 and will be a draft until 11485 is merged
What did you do?
Refactored library Router.
Why did you make this change?
The code looks cleaner, we don't need to define each possible library route in
buildapp.py
andAnalysisRouter.js
anymore,LibraryFolderRouter
will take care. Also it adds consistency in router naming.Additionally it fixes a following bug:
it was not possible to return into upper library folder with the 'back' browser button, this PR will fix this issue
How to test the changes?
Quite a few selenium tests are already in place
Go to libraries and surf, also use back <- and front -> buttons in your browser