We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At https://www.gatsbyjs.org/docs/gatsby-internals-terminology/#matchpath, the link under find-path.js is missing in the source.
find-path.js
But on the frontend, when resolving the page from the path (find-path.js), it is used (via reach router) to find the matching page.
The link to "pages are sorted" in the next paragraph is broken too.
Note that the pages are sorted so that those with matchPaths are at the end, so that explicit paths are matched first.
The text was updated successfully, but these errors were encountered:
there is a warning at the top of this doc, that this is outdated...
see also #24228
Sorry, something went wrong.
I'll close this in favor of #14228 - with Incremental builds in OSS now in Gatsby v3 some more things have changed
wardpeet
No branches or pull requests
At https://www.gatsbyjs.org/docs/gatsby-internals-terminology/#matchpath, the link under
find-path.js
is missing in the source.The link to "pages are sorted" in the next paragraph is broken too.
The text was updated successfully, but these errors were encountered: