-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
fix(gatsby-source-contentful): avoid confusion of Gatsby node and Contentful node count in logs #34830
Merged
LekoArts
merged 1 commit into
master
from
fix/contentful-avoid-confusion-with-node-duplication
Feb 17, 2022
Merged
fix(gatsby-source-contentful): avoid confusion of Gatsby node and Contentful node count in logs #34830
LekoArts
merged 1 commit into
master
from
fix/contentful-avoid-confusion-with-node-duplication
Feb 17, 2022
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
gatsbot
bot
added
the
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
label
Feb 16, 2022
TylerBarnes
approved these changes
Feb 16, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense since a node in each locale is for the same content, right?
LekoArts
added
topic: source-contentful
Related to Gatsby's integration with Contentful
and removed
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
labels
Feb 17, 2022
LekoArts
changed the title
fix(contentful): avoid confusion of Gatsby node and Contentful node count in logs
fix(gatsby-source-contentful): avoid confusion of Gatsby node and Contentful node count in logs
Feb 17, 2022
LekoArts
deleted the
fix/contentful-avoid-confusion-with-node-duplication
branch
February 17, 2022 08:04
@TylerBarnes correct! |
This was referenced May 26, 2022
This was referenced May 26, 2022
This was referenced May 26, 2022
This was referenced May 26, 2022
This was referenced May 26, 2022
This was referenced May 28, 2022
This was referenced May 28, 2022
This was referenced Jul 21, 2022
This was referenced Mar 28, 2023
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.
In #34584 we improved logging to separate between new and updated nodes.
For the existing ones, we forgot to divide by locale count. As multiple existing Gatsby nodes reflect one single Contentful node, this should make it more clear how many Contentful nodes the system already knew on a warm build.