Lars Hvam
Lars Hvam
Hi, When activating abapGit standalone, the editor gives the following warnings regarding the abapdoc, ref https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-us/abendoccomment.htm 750 SP0022 and 750 SP0006 seems okay on 754 SP0002 https://help.sap.com/doc/abapdocu_754_index_htm/7.54/en-US/abennews-752-abap_doc.htm guess there is...
In ABAP, everything is stored in a relational database. JSON files can be edited manually in any editor, The developer can edit the JSON files changing any sorting of arrays,...
Tooling
we can talk about this in the next call
Meta issue, I'll update the list, - [ ] INTF, #44, #53, #54, #83, #106, #128 - [ ] CHKO, #138, and the generic issues from INTF - [ ]...
`required` vs `showAlways` https://github.com/SAP/abap-file-formats/blob/main/doc/specification.md#required-fields there is a subtle difference, users can choose not to fill showAlways fields, but that would lead to differences after serialization
suggest: * add comment regarding the schema version * add comment regarding use of lowerCamelCase(?) for naming of JSON fields
with the overall design questions and decisions, I did not get to actually looking at the file, this task is a reminder
B: "Extreme Values", is this feature needed? I expect the schema generation to be based on the ABAP types C: "Length Specification", is this feature needed? I expect the schema...
https://github.com/SAP/abap-file-formats/blob/main/doc/specification.md#file-names ABAP should go into ABAP files, one file, like its presented to the developer in Eclipse Metadata for a object(R3TR) should go into a single metadata file per object,...