You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This breaks the unit test it('should route to the first entry in tabConfiguration array by default'...) but the my app and the example app both appear to work correctly with the change. I'm not sure how to fix the test: it seems events fire differently in a regular browser?
Can you please take a look at the latest in tab-in-index-page branch - i've added an option for this use case which should keep the existing behaviour for other cases. Look at README.md for an explanation of auto-select-default-tab.
If you're happy with this it'll get into master and released.
Ok i've changed my approach - i've removed the default route change code entirely. If people want to deep-link they can link directly to the tab-selected routes.
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.
...etimes
Attempts to fix #15
This breaks the unit test
it('should route to the first entry in tabConfiguration array by default'...)
but the my app and the example app both appear to work correctly with the change. I'm not sure how to fix the test: it seems events fire differently in a regular browser?