Gatsby: [gatsby-source-wordpress] Option to "include" routes, rather than only exclude routes
Description
Feature request: WordPress plugins often throw a lot of extra junk into the WordPress json-api, it would be helpful to have the ability to define included routes (which would exclude ALL routes except the ones that match the condition). Currently gatsby-source-wordpress only has the ability to exclude routes. Something like the below would be very helpful! thanks!
includedRoutes: ["/*/*/posts", "/*/*/pages", "/*/*/media"],
samburgers
All 8 comments
If You (or anyone else) would like to take a stab at this - here's where wordpress plugin filters endpoints before doing requests - https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-source-wordpress/src/fetch.js#L401-L456
pieh
on 7 May 2018
This is a really interesting idea — it might even make sense to make this as a default. I fairly regularly hear about someone trying Gatsby + WP than getting annoyed at it taking many minutes to sync everything from WP. It's a really bad first impression. It'd be better to only expose a subset of info that covers ~80% of use cases and then let people add more routes as needed.
To do this we'd need a way to make it really easy though to figure out what new routes need added as I can see people getting confused about that as well — UX tradeoffs! :-)
KyleAMathews
on 7 May 2018
I'll add my vote for this feature, unfortunately my coding skills currently aren't good enough to help implement this
scruffydan
on 16 May 2018
Yes please!
When pulling data from big WordPress projects it can take a really long time to get it up and running, and it's beyond counter intuitive to go through all possible routes and exclude them, when I just want to pull posts, for example.
Aionictic
on 18 May 2018
I might take a stab at implementing this.
dmackerman
on 22 Jun 2018
@dmackerman check https://github.com/gatsbyjs/gatsby/pull/6036 - @lightstrike already started doing some work on this
pieh
on 22 Jun 2018
@pieh Shouldn't this be closed since #6036 was merged?
ghost
on 25 Oct 2018
@openmedi You are right! Thanks for ping
pieh
on 25 Oct 2018
Related issues
Oppenheimer1
·
3Comments
dustinhorton
·
3Comments
kalinchernev
·
3Comments
jimfilippou
·
3Comments
ferMartz
·
3Comments
Most helpful comment
This is a really interesting idea — it might even make sense to make this as a default. I fairly regularly hear about someone trying Gatsby + WP than getting annoyed at it taking many minutes to sync everything from WP. It's a really bad first impression. It'd be better to only expose a subset of info that covers ~80% of use cases and then let people add more routes as needed.
To do this we'd need a way to make it really easy though to figure out what new routes need added as I can see people getting confused about that as well — UX tradeoffs! :-)