rshackleton/gatsby-transformer-kontent-image

Transforms assets from Kontent.ai into nodes usable by Gatsby Image

gatsby-transformer-kontent-image's Issues

Add support for base64 encoded data URIs

Describe the solution you'd like
Add support for the base64 field on fixed, fluid and resize resolvers to enable the "blur up" effect in Gatsby Image.

Describe alternatives you've considered
N/A

Additional context
N/A

Getting null values for height and width

Love the idea here, just running into a problem. When I try to use local images, I end up with null values for height and width of images.

I have the proper values under contract, but they don't appear in fixed, fluid, or resized. This means the srcSets also have a lot of NaN for the values.

I'd like to be able to use the srcSet functionality if possible. Any hints what I could change to get there?

Document the common use-cases

Is your feature request related to a problem? Please describe.
Using the plugin is not currently clear.

Describe the solution you'd like
Describe how the plugin should be used in a project and how the fragments can be used to populate the Gatsby Image component.

Describe alternatives you've considered
N/A

Additional context
N/A

Add tests!

Is your feature request related to a problem? Please describe.
Proper test coverage is necessary in order to have confidence in release new versions with CI/CD.

Describe the solution you'd like
Add test coverage for custom transformation logic when implemented. Investigate whether it is feasible for the local option; however this is a thin wrapper on gatsby-source-filesystem so should be fairly stable.

Describe alternatives you've considered
N/A

Additional context
Example test scenarios for an existing transformer plugin.

https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-transformer-yaml/src/__tests__/gatsby-node.js

Add other fragments for common requirements

Is your feature request related to a problem? Please describe.
When using other Gatsby Image compatible plugins there are typically fragments that explicitly include base64 data URIs and/or WebP support.

Describe the solution you'd like
Add more fragments to the existing fragments.js file.

Describe alternatives you've considered
N/A

Additional context
N/A