Fix documentation title sequence warnings#15337
Fix documentation title sequence warnings#15337sanjana2505006 wants to merge 6 commits intoapache:7.0.xfrom
Conversation
Adjusts heading levels in included AsciiDoc files and uses leveloffset to resolve 'section title out of sequence' warnings.
|
@jamesfredley Whenever you get a chance, please review and let me know if any changes are needed |
|
@sbglasius Whenever you get a chance, please review and let me know if any changes are needed |
| @@ -44,27 +44,31 @@ public String getName() { | |||
| public String getSourcePath(String path, Language language) { | |||
There was a problem hiding this comment.
The changes to this file don't appear to be material. We should revert them.
|
@sanjana2505006 can you please generate the single guide prior to your change & with this change? Then attach the results to this PR to assist in our review? |
|
The changes to TestFramework.java are purely cosmetic: they adjust line breaks for readability, remove an extra space, and convert a switch expression to a statement. These don't alter functionality, so reverting them is fine if the original style is preferred. No logic changes detected. |
|
Hello @jdaugherty, hope you're doing well. I wanted to follow up on the status of this PR whenever it's convenient for you. |
✅ All tests passed ✅🏷️ Commit: c721a4b Learn more about TestLens at testlens.app. |
|
I checked this out and reran the build on this, I'm still seeing the section title otu of sequence warnings: Rendering document file hookingIntoRuntimeConfiguration.adoc These warnings too: WARNING: programmaticTransactions.adoc: line 59: section title out of sequence: expected level 1, got level 3 |
01ede05 to
504875a
Compare
My bad, I missed that those specific files were still throwing warnings. I’ve updated the fragment structure to use Level 0/1 headers and adjusted the |
Fixes #14898.
I fixed the "section title out of sequence" warnings by adjusting the header levels in the .adoc files and using
leveloffsetin index.adoc to keep them consistent.(Note: I couldn't find
eventsAutoTimestamping.adocin the repo, so I applied the fix to the other files that were throwing the same warning.)