DDLS: Make the .objectdependencies.json file of the DDLS object type prettier

[BeckerWdf]

Currently this json file can be improved in different ways:

1. it could be formatted (indented) like the other json files
2. UPPERCASE names could be converted to camelCase
3. a JSON schema should be provided

[albertmink]

With regard to the formatting

The Github action says, that the file has been checked
https://github.com/SAP/abap-file-formats/runs/3321557726?check_suite_focus=true#step:4:203

Something goes wrong here, since the formatting should follow the definition here

abap-file-formats/.editorconfig

Line 14 in 645506a

[*.json]

[larshp]

4. alternatively add it into the main object json file, so there is just one json file and one schema for the object type

[BeckerWdf]

4. alternatively add it into the main object json file, so there is just one json file and one schema for the object type

We want to keep it separate.

[larshp]

why?

its a generic abap-file-format discussion, I think collecting the metadata of each object into one file makes it easier,

• for the developer to figure out what has changed
• keeping track of possible schema changes, if the there are multiple files and multiple schemas, not having cross dependencies makes it easier

another thing, I can see this specific json file as redundant, https://github.com/SAP/abap-file-formats/blob/main/README.md#background-and-scope, the information is just replicating already existing information?

plus it is not something that the developer creates/maintains/is interested in

[BeckerWdf]

why?

Because they serve two different purposes. The data in the main file is something a developer (at least) partially want's to review.
The .objectdependencies.json contains only information that is needed for the activation in the target system. So for the pure code review use case this is is not relevant (and the user can simply skip / ignore it).
For the "transport" use-case it's absolutely needed.

[albertmink]

This topic applies in a wider context to many object, see comment here, in particular the last sentence. Unfortunately, it is not an easy decision - yet ;)

[BeckerWdf]

This topic applies in a wider context to many object, see comment here, in particular the last sentence. Unfortunately, it is not an easy decision - yet ;)

I don't understand your point. This file is not about translation.

[albertmink]

my bad, too much translations transports in my head. Anyhow, there are files ( for transport #131 , translation #106 , documentation #130 and more to come) for which we need to find a solution of how to do a proper Abap file format.

[larshp]

ref https://github.com/SAP/abap-file-formats/blob/main/README.md#background-and-scope

plus no obsolete or redundant information as well as no autogenerated content

from a developer perspective, I know the ABAP CDS syntax, I fire my my favorite editor = notepad, enter the CDS, save as object.ddls.acds, this should be it, no additional files required(unless the description for DDLS is required)?

transport and activation, that part is somewhat circumstantial. It would correspond to having to maintain a list of methods in a different file than the ABAP file containing a class implementation.

[BeckerWdf]

transport and activation, that part is somewhat circumstantial. It would correspond to having to maintain a list of methods in a different file than the ABAP file containing a class implementation.

So we only focus on code review? Don't we want to transfer also a CDS model from one system to another?