Fix for Issue #183: MailMerge and totally unrelated nested fields #185
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
These changes for MailMerge ignore and preserve nested fields that may or may not contain MERGEFIELDs. Nested fields in an imported docx can cause a stack overflow in FieldRef.java:304 (which logs the detection of nested fields...).
|
Will the conflicts be resolved and this PR merged anytime soon? I just ran across this very issue with docx4j 8.3.4, and this PR looks like it will solve it. |
|
The stack overflow problem (because of recursive logging statement) is still present in 11.4.8 |
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.
These changes for MailMerge ignore and preserve nested fields
that may or may not contain MERGEFIELDs.
Nested fields in an imported docx can cause a stack overflow
in FieldRef.java:304 (which logs the detection of nested fields...).