-
Notifications
You must be signed in to change notification settings - Fork 34
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-source-s3): download non-image files #225
Comments
@robinmetral may know the answer. If there's no particular reason I'd be happy to accept a PR. |
I was trying to understand why it doesn't process my markdown files. I believe |
@sebhewelt You interested in contributing such an enhancement? |
Hey folks, I'm super sorry for the extremely late reply here, I had ignored notifications on this repo for some reason 🙈 This was previously requested for tl;dr there is no specific design reason weighing against this. The only challenge is that the plugin was built specifically to download image files for processing by sharp, not for any other purpose—so I'm not sure what exactly needs to change beyond removing this
For example it's possible that the schema needs to be different, depending on what you'd like to do with your files. This would probably require some fiddling/testing but can probably be done 🙂 I unfortunately don't have any time to implement this (and I haven't worked with Gatsby for some time, so would probably not be the best person to do it). But consider this a green light for a contribution 🟢 |
Co-authored-by: Renovate Bot <[email protected]>
I'd like to be able to retrieve files other than images from S3, and access them through GraphQL.
Currently, localfile nodes are only generated in GraphQL for image files, and not e.g.: mdx, json or other data/text files.
I'm specifically interested in mdx files (which I assume could then be ingested by gatsby-transformer-mdx).
Is there a design reason for only creating local file nodes for images? If there are drawbacks to handling all files, a config option for other file extensions to accept seems like a clean solution, e.g.:
{ resolve: 'gatsby-source-s3', options: { aws: { ... }, buckets: [...], file_extensions: ['.mdx', '.json'], },
The text was updated successfully, but these errors were encountered: