-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: fedWireMessage is an object, not an array #358
Comments
Yea.. We'll need to make this change. I think a breaking change is appropriate since this is such a major bug. |
Thanks @DennyWeinberg. I'll be addressing this one soon. |
Any news here? |
I've been asking around for sample files to see how bulk/batch files should be formatted, but haven't been able to find anything. I'll get back to researching this next week. |
Any news here? :) |
I haven't been able to find much info about how batch files should be formatted. Do you have any example files you can share @Denny-g6labs? |
@Denny-g6labs If you have the ability to run some files through PR #394, any feedback would be appreciated. I'd love to hear how those changes handle files from various financial institutions. |
WIRE Version
v0.15.0
What were you trying to do?
I'm creating, parsing and validating WIRE files that contains multiple transactions.
What did you expect to see?
A parsed JSON structure containing all my fed wire messages.
What did you see?
A parsed JSON structure containing ONLY the last fed wire message, others are lost.
The problem is, the API JSON is not a list: https://moov-io.github.io/wire/api/#post-/files/create
So how could that hold multiple messages? fedWireMessage should be an array, not an object.
How can we reproduce the problem?
The text was updated successfully, but these errors were encountered: