-
Notifications
You must be signed in to change notification settings - Fork 71
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
Bootstrap upgrade #186
Bootstrap upgrade #186
Conversation
Don't know either, the migration guide is a bit long and we don't really use that much. Maybe by going through
Yes, please. To have the profile dropdown in the leftmost position of the screen, in order not to hide the route while trying out various profiles and see how the route changes. Also, I thought it just looks weird to open this huge dropdown somewhere in the middle of the screen. |
50cc6ea
to
dea9466
Compare
OK I think this is it - reviews are always welcome :). |
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.
Looking good overall.
Some things I found:
- the stats labels in the footer are not hidden on small/mobile screens
- the profile message (warning after upload / on error) is not visible, just blank space
- the delete route modal title is messed up (bootbox)
Thanks, indeed I missed some. Fortunately there were easy fixes. Regarding the modal issue, I have to upgrade |
Hmm, we are actually filtering out One way is to use the non minified file instead: "bootbox": {
"main": [
"src/bootbox.all.js"
]
}, But the other way would be to just use |
Thanks a lot for taking on this tedious task! |
I think so, but can't remember why. Probably because some projects had both the src and min files in their I think I haven't seen a case yet where we would have needed the minified file, non-minified or source files were always available and sufficient. bower.json spec says:
The reason for me is to have non-minified library code available for debugging and proper stack traces, both in debugging mode and also in the release sourcemap. |
Fixes #107
I'm not sure how this should be tackled. For now I'm just trying to fix broken things.
Still to do: