Fix mixed-case H1 prefix when rendered #3003
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
Signed-off-by: tim.quinn@oracle.com <tim.quinn@oracle.com>
barchetta
approved these changes
May 10, 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.
Resolves #3002
The H1 line was followed by a blank line and then the
h1Prefixdefinition.It appears that either
h1Prefixmust be defined earlier in the file than the H1, orh1Prefixdefinition must be in the attribute assignment block immediately following the H1 line with no intervening blank lines.Moving all attribute assignments before the H1 line resolved this.
Signed-off-by: tim.quinn@oracle.com tim.quinn@oracle.com