This repository was archived by the owner on Sep 22, 2023. It is now read-only.
Parse :86: field as additional information relating to statement #13
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
Fixes issue raised in webschik#12, where an `:86:` field relating to the statement as a whole was being parsed as relating to a specific transaction.
|
A note regarding the logic: see statement in MT 940 Network Validated Rules:
Therefore, if the current transaction already has |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes issue raised in #12, where an
:86:field relating to the statement as a whole was being parsed as relating to a specific transaction.Note that there was an extraneous space character in the
ing-1.mta, which was allowing the test to pass when it should not have.