Fix links to docs chapters #36
Merged
Conversation
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
mcg-web
approved these changes
Nov 9, 2022
Contributor
|
Thank you @andrew-demb ! |
Contributor
Author
|
@mcg-web should we drop mention about "Define a custom GraphQL endpoint" from readme since it was dropped before? |
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.
There is no docs for custom parameters and custom GraphQL endpoint, which were dropped in 1f70305#diff-769b4cd82eac8712bf35bb9c552175b94ae31871b6e3dd20fdbe7f1994172e12
Was it on purpose? Should we drop their mention from readme?