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 fixes an incompatibility with the Sphinx version and the versions of other things as declared in the
requirements.txt
file for the docs. In the new version - 7.0.1 - there is now a lexer forapplication/x-www-form-urlencoded
-encoded content, which means that some of our blocks that declare this type of content no longer lex. In reality, these payloads will actually be parsed asapplication/json
no matter what's in theContent-Type
header; Traffic Ops doesn't consider it at all. But it works equally well if you actually do set the correct header, and that gives us back syntax highlighting, so I fixed/changed those.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build the docs, make sure there are no warnings, even when you use the build tools declared by
requirements.txt
. Other than that, we need to wait for RTD to pick this up before we'll know if it has any effect on those issues.If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist