DBZ-8450 Extra list-continuation (+) chars corrupt formatting of description lists#6010
Merged
jpechane merged 1 commit intodebezium:mainfrom Nov 25, 2024
Conversation
Contributor
|
@roldanbob Applied, thanks |
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
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.
DBZ-8450
This change removes extraneous list continuation characters (i.e., plus signs [
+]) from the descriptions of the Oracle connector propertieslog.mining.query.filter.modeandlog.mining.strategy.The documentation for the two Oracle connector properties uses definition list formatting to present information about the available configuration options. In an AsciiDoc definition list, a pair of colon characters represent the delimiter between the term being defined and its description. In the previous version of the documentation, the definition list formatting is incorrectly combined with the use of list continuation characters, i.e.,
+signs. As a result, instead of serving as markup characters, the colon characters render literally in the published content.