fix(gatsby-source-contentful): Remove whitespace from default long text value #21412
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sidharthachatterjee
added
the
bot: merge on green
mrseanbaines
deleted the
fix/gatsby-source-contentful-long-text-whitespace
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As described in the linked issue, currently when querying an empty "long text" field with the
gatsby-source-contentfulpackage, a string with a single whitespace character is returned. It seems this whitespace serves no purpose and makes falsy checks unintuitive and overcomplicated. This PR simply removes the unnecessary whitespace.Related Issues
Fixes #20579