Skip to content
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

[gatsby-source-wordpress] excludedRoutes as a function #13270

Closed
kyuumeitai opened this issue Apr 10, 2019 · 5 comments
Closed

[gatsby-source-wordpress] excludedRoutes as a function #13270

kyuumeitai opened this issue Apr 10, 2019 · 5 comments
Labels
stale? Issue that may be closed soon due to the original author not responding any more.

Comments

@kyuumeitai
Copy link

Hi there. I was wondering if it's possible to have excludedRoutes as a function, for instance, to filter certain media files from all posts with certain tag.

I have several gatsby instances with one WordPress, and every time that I build one of the gatsby projects, it includes all media files.

Thank you.

@sidharthachatterjee
Copy link
Contributor

@kyuumeitai If I understand correctly, this would help in use cases where a glob isn't sufficient because some context is required on a certain route (in this case, a tag)?

I have several gatsby instances with one WordPress

We could certainly support this but just wondering if this is a popular use case.

@kyuumeitai
Copy link
Author

Indeed, this could help if you have several clients with one wordpress installation.

Another case would be if you need to publish a lean gatsby wordpress site with only the images that are being actually used, i.e., you have 100 photos in media but you have 3 posts with one featured_media, the build process would grab the 100 photos even if you use only 3.

@frinyvonnick
Copy link
Contributor

Do you have some examples of usage for this function ?

@gatsbot gatsbot bot added the stale? Issue that may be closed soon due to the original author not responding any more. label May 14, 2019
@gatsbot
Copy link

gatsbot bot commented May 14, 2019

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’s 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! 💪💜

@gatsbot
Copy link

gatsbot bot commented May 25, 2019

Hey again!

It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it.

Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m HUMAN_EMOTION_SORRY. Please feel free to reopen this issue or create a new one if you need anything else.

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/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks again for being part of the Gatsby community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale? Issue that may be closed soon due to the original author not responding any more.
Projects
None yet
Development

No branches or pull requests

3 participants