fix documentation build warnings #1401
Merged
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
rosik
reviewed
Apr 29, 2021
| @@ -370,7 +370,7 @@ Fixed | |||
|
|
|||
| - Properly handle nested input object in GraphQL: | |||
|
|
|||
| .. code-block:: graphql | |||
| .. code-block:: text | |||
There was a problem hiding this comment.
There's no graphql lexer provided with Pygments. However, we can try using https://pypi.org/project/pygments-graphql/.
Onvember
force-pushed
the
onvember/fix-doc-build-warnings
branch
3 times, most recently
from
5285127
to
457d755
Compare
rosik
force-pushed
the
onvember/fix-doc-build-warnings
branch
from
0cc2903
to
ac0ce6f
Compare
rosik
approved these changes
May 13, 2021
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.
This PR fixes some warnings while building the docs.
fixes part of #903