-
Notifications
You must be signed in to change notification settings - Fork 61
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
Object types do not support ABAP language version keyUser
#320
Comments
again, I'd argue to remove the language version from the object definitions, what if NROB sometime is supported in keyUser? Then the object definition must be changed, but its just another runtime that supports the object |
I don't think we can remove the ABAP language version as it is stored per object. This design, IMHO, cannot be changed by ABAP file formats. See #44 If new enum values appear in the future, it will be added. We have the same issue for all other enumerations. Currently, we consider this as compatible change. See: https://github.com/SAP/abap-file-formats/blob/main/docs/json.md#format-versions-and-compatibility
|
the file format does not need to directly reflect the implementation in the system, eg. specific names and/or fields 🎪 |
Sorry, I don't understand what you mean |
just going in circles 😁 #44 |
Also fixed with https://launchpad.support.sap.com/#/notes/3138884 This Note has been already linked in abapGit/abapGit#5279 |
Following object types actually do not support ABAP language version
keyUser
, but specify this in their enum values:The text was updated successfully, but these errors were encountered: