-
Notifications
You must be signed in to change notification settings - Fork 80
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
Occurs depending on mappings #151
Comments
Yes, this makes sense overall. But how a mapping can be defined? Is it a part of the copybook or need to be specified via |
It would have to be done through an option. I'm not sure if this is standard at all, but the files I have are structured this way. |
Makes sense. Could you please give an example of such a mapping? Can it be several mappings for different OCCURs? How urgent is this? The current plan is to
Have pressure from other projects, was planning to work on releasing 1.0.0 sometime next week. |
No hurries at all. The idea would be to specify for each field that depends on something else a mapping. With the example I had before:
A possible OCCURS mapping (json) would be
|
Actually, a better example would be
and the JSON mapping
|
Yes, this makes sense. Thanks! |
I have a few copybooks that have groups occurring depending on a flag on some field as follows:
In this example, if
FIELD_TYPE
isA
, then onlyRECORD_TYPE_A
is defined. Same forB
.Maybe we could support something like this by allowing
OCCURS
clauses to point to non-integer fields together with some sort of mapping.If this sounds good, I can come up with a PR that does this.
The text was updated successfully, but these errors were encountered: