Render pages content in order #651
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
|
cc: @utzig |
gmarull
force-pushed
the
feature/render-pages-content-in-order
branch
from
ed79525
to
6768147
Compare
When rendering Doxygen pages one expects content to appear in the written order. As of today `para` sections content was grouped separately depending on its type, causing out-of-order content in some pages. Signed-off-by: Gerard Marull-Paretas <[email protected]>
gmarull
force-pushed
the
feature/render-pages-content-in-order
branch
from
6768147
to
a46be23
Compare
|
@utzig @vermeeren can you review? thanks |
|
@michaeljones can you review? thanks |
|
@vermeeren @michaeljones would you mind creating a new release? Thanks! |
|
@gmarull v4.28.0 is now released containing this PR. |
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.
When rendering Doxygen pages one expects content to appear in the
written order. As of today
parasections content was groupedseparately depending on its type, causing out-of-order content in some
pages.
Fixes #648