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-transformer-sharp] Remove the width/maxWidth default values #7680

Merged
merged 1 commit into from
Aug 28, 2018
Merged

[gatsby-transformer-sharp] Remove the width/maxWidth default values #7680

merged 1 commit into from
Aug 28, 2018

Conversation

Windvis
Copy link
Contributor

@Windvis Windvis commented Aug 27, 2018

As of this commit gatsby-plugin-sharp can now calculate the image's width based on its height but for that the work the default values need to be removed.

I chose to simply remove the values since gatsby-plugin-sharp adds default values when both width and height aren't set (and the same goes for maxWidth/maxHeight).

Fixes: #7663

Note: This depends on the changes in this pr to work. Otherwise the width will be set to NaN and Sharp will throw an error.

gatsby-plugin-sharp can now calculate the image's width based on its height but for that the work the default values need to be removed
@Windvis Windvis changed the title gatsby-transformer-sharpRemove the width/maxWidth default values [gatsby-transformer-sharp] Remove the width/maxWidth default values Aug 27, 2018
@pieh
Copy link
Contributor

pieh commented Aug 28, 2018

Just checking here - in your description "[this pr]" refers to #7671 ?

@Windvis
Copy link
Contributor Author

Windvis commented Aug 28, 2018

O woops, yes I forgot to include the link 😶 My bad 😬

Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants