Closed
Conversation
…cope, and be a bit more transparent, also some code cleanup
…g extensions, added top navbar to every page
…ve timepicker opening button
Contributor
Author
|
Test failures are totally valid: |
Contributor
|
All those tests are related to the navbar injection, which doesn't work the same way anymore. The test cases should probably be translated to the kbn-top-nav or navbar-extensions directive though, as it should work the same there. EDIT: I think you really just need to check the kbn-top-nav throws if it doesn't have a name attribute. All the tests around the button group checks aren't valid anymore. |
Contributor
Author
|
Closing in place of #6657 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is basically the same as #6657, buy with linting fixed and the couple other bugs that @w33ble and i found taken care of.