-
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
feat(gatsby): override default options of gatsby-plugin-page-creator #17379
Comments
Hey @wardpeet! I would like to work on this issue. |
Nice! Please let us know if we can assist with anything. We suggest opening a draft/WIP PR if you having questions so we can give pointers on specific areas. Thank you for contributing! ❤️ |
My PR is failing e2e tests even though all other tests are passing in my local dev environment. Any idea @wardpeet |
Fixed and published in |
Thanks @sidharthachatterjee @akshayymahajan @wardpeet ! This is working with the following config in my {
resolve: `gatsby-plugin-page-creator`,
options: {
path: `${__dirname}/src/pages`,
ignore: [`**/examples/**`],
},
}, |
@karlhorky We meet again! Put you've got the wrong Sid this time 😛 (you want @sidharthachatterjee) |
🤦♂️ Ah oops, sorry Siddharth! Tagged Sidhartha now. |
Summary
When a user specifies a
gatsby-plugin-page-creator
plugin with a path pointing tosrc/pages
we replace the config of our defaultgatsby-plugin-page-creator
in gatsby core. This allows people to addignore
options.A step in the right direction:
gatsby-plugin-page-creator
plugin with the path pointing to src/pages and temporary save the config in a variablegatsby/packages/gatsby/src/bootstrap/load-plugins/load.js
Line 217 in abf8881
Basic example
Should change the default
gatsby-plugin-page-creator
config ingatsby/packages/gatsby/src/bootstrap/load-plugins/load.js
Lines 214 to 222 in abf8881
Outcome should be
Motivation
We get a lot of requests to override the default
gatsby-plugin-page-creator
plugin. At this point we don't offer a good solution for this problem, there is a workaround but it's not fixing all use cases.The text was updated successfully, but these errors were encountered: