Feature: support for DatoCMS source #91
Conversation
|
One thing to note: I slightly changed the caching key, it now includes the provider in the key (so caching is different for each source). I'm not sure if this is a useful change, but it made sense as this transformer would now service multiple sources |
|
Added: resolver for DatoCmsFileField, otherwise the resolver would not be usuable for files added to other models. |
README.md
Outdated
| ## Features | ||
|
|
||
| * Read content of your SVG files from `gatsby-source-contentful` and `gatsby-source-filesystem`. | ||
| * Read content of your SVG files from `gatsby-source-contentful`, `gatsby-source-datcms` and `gatsby-source-filesystem`. |
|
Sorry I overlooked this 🙈 Could you fix the typo pls? I'll then try to run it on my machine, as GH won't run the CI |
|
Fixed the typo, but apparently my last few commits weren't signed properly. Have to check what happened here |
|
Just realized I don't sign commits locally at all, is this something that is absolutely required for the merge? |
|
Nono, its just that the CI won't run then. I'll have to test locally. |
2 participants
Added the feature, tets and documentation.
Would be a great addition for those using Dato