-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Configure ScopedHistory consistently regardless of URL used to mount app #75074
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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 file contains 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 file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -54,6 +54,9 @@ export default function ({ getService, getPageObjects }: PluginFunctionalProvide | |
}); | ||
}; | ||
|
||
const navigateTo = async (path: string) => | ||
await browser.navigateTo(`${PageObjects.common.getHostPort()}${path}`); | ||
|
||
describe('ui applications', function describeIndexTests() { | ||
before(async () => { | ||
await PageObjects.common.navigateToApp('foo'); | ||
|
@@ -63,6 +66,15 @@ export default function ({ getService, getPageObjects }: PluginFunctionalProvide | |
await testSubjects.existOrFail('fooAppHome'); | ||
}); | ||
|
||
it('redirects and renders correctly regardless of trailing slash', async () => { | ||
await navigateTo(`/app/foo`); | ||
await waitForUrlToBe('/app/foo/home'); | ||
await testSubjects.existOrFail('fooAppHome'); | ||
await navigateTo(`/app/foo/`); | ||
await waitForUrlToBe('/app/foo/home'); | ||
await testSubjects.existOrFail('fooAppHome'); | ||
}); | ||
Comment on lines
+69
to
+76
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tried to find a way to test this more directly but wasn't able to find a good way of doing so without depending on the implementation details of ScopedHistory. Replicating the buggy behavior in #75051 seemed like the best option available. |
||
|
||
it('navigates to its own pages', async () => { | ||
// Go to page A | ||
await testSubjects.click('fooNavPageA'); | ||
|
@@ -72,7 +84,7 @@ export default function ({ getService, getPageObjects }: PluginFunctionalProvide | |
|
||
// Go to home page | ||
await testSubjects.click('fooNavHome'); | ||
await waitForUrlToBe('/app/foo'); | ||
await waitForUrlToBe('/app/foo/home'); | ||
await loadingScreenNotShown(); | ||
await testSubjects.existOrFail('fooAppHome'); | ||
}); | ||
|
@@ -86,7 +98,7 @@ export default function ({ getService, getPageObjects }: PluginFunctionalProvide | |
|
||
it('navigates to app root when navlink is clicked', async () => { | ||
await appsMenu.clickLink('Foo'); | ||
await waitForUrlToBe('/app/foo'); | ||
await waitForUrlToBe('/app/foo/home'); | ||
// await loadingScreenNotShown(); | ||
await testSubjects.existOrFail('fooAppHome'); | ||
}); | ||
|
@@ -105,7 +117,7 @@ export default function ({ getService, getPageObjects }: PluginFunctionalProvide | |
|
||
it('can use the back button to navigate back to previous app', async () => { | ||
await browser.goBack(); | ||
await waitForUrlToBe('/app/foo'); | ||
await waitForUrlToBe('/app/foo/home'); | ||
await loadingScreenNotShown(); | ||
await testSubjects.existOrFail('fooAppHome'); | ||
}); | ||
|
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.
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.
Note that I did not fix the legacy route below. Changing it caused a lot of test failures + no apps are currently using this and it is slated for removal in #74911
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.
Can't find proper documentation for it, what is the actual difference between
match.url
andmatch.path
?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.
From the docs:
From what I can gather,
path
will always be the path that was passed to the Route component that matched, whileurl
will be the portion of the URL that matched. I think that can include the/
, whereas ourpath
never has a trailing slash unless the application explicitly includes on in theappRoute
parameter.