Marc Bernard

@rayatus you can try #6320

Hi Frank, this goes in a direction that's also of general interest (mine, too): Clear separation of UI, repo, and object layers in the abapGit code The question is how......

I think right direction but such big changes can't be done via texting here. There are over two dozen open refactoring issues, many related. Peacemeal PRs might make it worse....

The implementation should certainly have the interface prefix. That's a bug in SAP to allow it without, imho. Is it a bug in AG when deserializing the class or SAP...

Nice analysis. As long as there are diffs, we can live with it. For AG itself, the answer is to eliminate the aliases. A general solution would be to drop...

Goes both ways: repos with several object type make debugging harder and runtime longer. But you also might expose dependency issues. In general, each object type should have its own...

Isn't this data included in object type `SUSH` (supported already but only for newer releases)?

the code doesn't exist in my 753. Maybe 754 + ADT?

Rather than removing `scalar_function`, the repo should be updated. Like many other objects. But it looks like SAP is not interested in updating this repo to be inline with current...

whew, that's a lot. first, I'm much more optimistic when it comes to "seamless deployment". I fixed dozens of bugs in this area and in general it works very well....