[BUGFIX] Ensure nested w:sdt -> w:sdtContent node parsing for Document
#2599
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
Nodes can be nested or directly provided for the document structure. Until now, the `sdt->sdtContent` wrapping have not been respected. This change moves the node parsing for a document to a dedicated method and make it recursivly callable to unnest the wrapped node.
sbuerk
changed the title
w:sdt -> w:sdtContent node paresing for Documentw:sdt -> w:sdtContent node parsing for Document
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.
Nodes can be nested or directly provided for the document structure.
Until now, the
sdt->sdtContentwrapping have not been respected.This change moves the node parsing for a document to a dedicated
method and make it recursivly callable to unnest the wrapped node.