chore(gatsby-source-contentful): migrate to latest Contentful SDK#35501
Merged
KyleAMathews merged 9 commits intomasterfrom Jul 25, 2022
Merged
chore(gatsby-source-contentful): migrate to latest Contentful SDK#35501KyleAMathews merged 9 commits intomasterfrom
KyleAMathews merged 9 commits intomasterfrom
Conversation
axe312ger
added
the
topic: source-contentful
gatsbot
bot
added
the
status: triage needed
axe312ger
force-pushed
the
fix/migrate-to-latest-contentful-sdk
branch
4 times, most recently
from
26dfeb5 to
f933f20
Compare
axe312ger
added
status: needs core review
axe312ger
force-pushed
the
fix/migrate-to-latest-contentful-sdk
branch
from
f933f20 to
4e02d51
Compare
KyleAMathews
approved these changes
Jul 25, 2022
KyleAMathews
changed the title
This was referenced Feb 23, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
With v9, the error handling got updated. We have our own error processing in place, which had to be adjusted for this major version.
v10 of the SDK is already on the way, so let us stay up 2 date so we have less effort of migration and have all latest bugfixes included.