Add a new flag to control whether the presence of unsupported FpML elements triggers errors when parsing#2097
Merged
Merged
Conversation
…hether the presence of unsupported FpML elements triggers errors when parsing.
jodastephen
suggested changes
Oct 14, 2019
| * @param refData the reference data to use | ||
| * @return the document parser | ||
| */ | ||
| public static FpmlDocumentParser withLenientMode( |
Contributor
There was a problem hiding this comment.
Would be better to have public FpmlDocumentParser withLenientMode() which takes the instance you already have and returns a new instance with the flag flipped.
jodastephen
approved these changes
Oct 14, 2019
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.