Update instructions to provide users with clearer instructions #39111
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
Previous instructions were confusing because they didn't reflect what was being seen in GraphiQL.
gatsbot
bot
added
the
status: triage needed
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.
Previous instructions were confusing because they didn't reflect what was being seen in GraphiQL.
Description
Changed previous instructions to provide readers with clearer directions on how to sort the nodes in descending order, so that the newest posts come first.
Documentation
This feature is documented at the Task: Update the Blog page query to use the allMdx field instead of allFile section of the at this link Part 5: Transform Data to Use MDX.
Tests
No, I didn't add any test.
Related Issues