-
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
filenames, when to use subobjects? #115
Comments
Thanks, for the proposal. I am struggling whether we really should go this way for the following reasons:
|
scoping & conventions over exceptions |
Lets take an example PROG ZFOOBAR, serializing each LIMU could give the following files(?)
Serializing all JSON into single file would give
|
Putting all the ABAP code into one *.abap file is trivial for reports but already cumbersome for classes for the reasons @schneidermic0 mentioned (like mapping LIMU METH changes to the one implementations include...) |
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, having eg. one metadata file per dynpro, per CUA etc. makes it more complex IMHO, more schemas, more things to check on serialization/deserialization time
Translations: something, I've not thought much about these yet, deferred to #106
The text was updated successfully, but these errors were encountered: