Coalesce field values to ensure no broken production build on no content #2882
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
|
On closer inspection this seems to be a duplicate of #2037 |
|
Deploy preview ready! Built with commit fafb654 |
|
Deploy preview ready! Built with commit fafb654 |
|
Yeah — would love it if someone wanted to help out on #2037. Also you'd need to emulate the type of the contentful field as you wouldn't want to default to a string when the original type is a number and so on. |
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.
Added one line check to ensure fields that are sent from contentful are not treated as null and then stripped from graphql available schemas.
Caused by behaviour described in #2881