-
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(gatsby-plugin-create-client-paths): don't process pages that already use matchPath #9220
Conversation
if `page.matchPath || page.path.match(/dev-404-page/)`, we should `resolve` **AND** `return`
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.
Good catch. Thanks @i8ramin!
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.
I don't mind this for clarity (I like to do this myself!) but is this actually true?
Here's an example in Runkit of this not working like you describe, right? Ha, whoops adding a log confirms you're right!
Nice catch, indeed!
Here is my local test of this. I put some WITHOUT (current)
WITH (patch)
|
Holy buckets, @i8ramin — we just merged your PR to Gatsby! 💪💜 Gatsby is built by awesome people like you. Let us say “thanks” in two ways:
If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’. Thanks again! |
…ady use matchPath (gatsbyjs#9220)
if
page.matchPath || page.path.match(/dev-404-page/)
, we shouldresolve
ANDreturn
closes #9221