Escape tags in a Camel recipe option description - #549
Merged
Merged
Conversation
Contributor
|
While we appreciate that you're attempting to improve the docs, please be aware that all files in the Please make changes to the recipes themselves rather than to these files. When the next release happens, these files will be updated accordingly. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 full recipe regeneration in 6707536 broke the Pages deploy. The `consumerOnly` option description on `ChangeXmlComponentUriRecipe` mentions `` and `` endpoints, which MDX parses as unclosed JSX tags. Until this merges, no deploy succeeds, and the recipe pages for 8.92.1 and 8.92.8 stay unpublished.