Alexander Tsybulsky
Alexander Tsybulsky
imho file-mask list would be more flexible. also allows to exclude specific object types for example. packages themselves, some xslts ... other internal only stuff.
> ... more concrete example ... Yeah, I also didn't think about it until I saw the real case with our real codebase :) Your example is actually OK, just...
Just thinking about scope and specification format ... so the idea is to be able to exclude: types of objects (not 100% that it is needed really, but ... e.g....
**Final solution**: - build a simplified path, from tadir item (from serialization - it has package path!): `/src/pkg/subpkg/obj.type`, so not xmls, the type is kind of file extension - check...
+1 It's super intransparent when the interface is created and then has to be manually added to transport after dumps in further systems. This process should be more accountable.
Not sure I understood the issue. What exactly are you doing with this json? Can you help with the UT case? I added a test of how I understand it...
no response, closing
In general I don't mind. But I don't have experience with `if_serializable_object`. The description looks useful. @larshp @mbtools Do you have any concerns for abapGit and other project you maintain?
I guess I need to remove also this ref to ensure serializer works ... maybe it's time, the deprecation banner is there for some time ...
Not quite sure how this works ... Help says: > To export objects that are referenced by reference variables, use the statement [CALL TRANSFORMATION](sapevent:ABAPCALL_TRANSFORMATION) to serialize and export these objects...