This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Fix TM API /publish/CrStates response example#6660
Merged
zrhoffman merged 1 commit intoapache:masterfrom Mar 15, 2022
Merged
Conversation
zrhoffman
approved these changes
Mar 15, 2022
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The current response example for the TM API's
/publish/CrStatesendpoint isn't syntactically valid, so syntax highlighting is broken. This PR fixes that.I also linked some
:term:s to the glossary, and removed a couple of repeated property explanations.Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Make sure the docs build, check the rendered example to verify syntax highlighting is done.
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist