This PR suggested adding custom validation and path manipulation to gastby-plugin-page-creator. In general we don't want to complicate plugin interfaces much. It's a better pattern to extract out logic into libraries that can be reused in multiple plugins or in a site's gatsby-node.js.
So this PR is around creating a separate library (it would be a package here in this repo) that extracts out the various bits of logic from gatsby-plugin-page-creator in a way that makes them reusable & overridable.
E.g. the library could export a few functions for:
Then someone that wants to create pages for a site but use their own custom logic could use the library to do so.
I would like to work on this issue 馃槃 I'll open a PR as soon as possible 馃憤
I named the package gatsby-page-helper. Sounds good to you @KyleAMathews 馃?
gatsby-page-utilities maybe?
Let me drag in @gatsbyjs/ecosystem & @gatsbyjs/core into this bikeshed 馃槃
gatsby-page-utils sounds nice! :-D
Thanks for jumping on this @frinyvonnick !
Hiya!
This issue has gone quiet. Spooky quiet. 馃懟
We get a lot of issues, so we currently close issues after 30 days of inactivity. It鈥檚 been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contributefor more information about opening PRs, triaging issues, and contributing!
Thanks for being a part of the Gatsby community! 馃挭馃挏