-
Notifications
You must be signed in to change notification settings - Fork 10.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
fix: use path prefix in navigate/replace/push calls #8289
Conversation
do |
@pieh yup, it should! I originally had a variant where they didn't, but they do! I validated with gatsby-dev-cli. Basically the behavior is unchanged, we'll pass through |
|
||
describe('navigate', () => { | ||
beforeEach(() => { | ||
cy.visit(`/`) |
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.
As info, waitForRouteChange()
wasn't working here. Will give it another shot in a bit just to validate I'm not crazy.
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.
was it timing out? I've tried some more involved stuff and didn't work for me today too but didn't dig into that yet
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.
@pieh yeah it was!
…sbyjs#8289) * fix: prefix navigate calls with pathPrefix Fixes gatsbyjs#8155 * test: fix unit tests and add a few new ones * e2e: update integration tests * test: standardize on trailing slash * fix: ensure parsePath still works the way it used to with path * style: run eslint * fix: use waitForRouteChange API
This PR fixes the behavior re: pathPrefix identified in #8155.
Essentially:
withPrefix
helper in all programmatic navigationLink