Add User-Exit in zcl_abapgit_oo_serializer methods

[AlexandreHT]

Method serialize_abap_clif_source in zcl_abapgit_oo_serializer contains a user exit (custom_serialize_abap_clif) that enables me to perform a custom Pretty print different from the one I use on my system (cf. https://gist.github.com/mbtools/71aa345a8ccb8f375568f9f337569154).

Such a User Exit is missing in the following methods:

• serialize_locals_def
• serialize_locals_imp
• serialize_macros
• serialize_testclasses

Thanks,

[mbtools]

it should be a "code post-processing" exit and also available for object types like prog, fugr, type, and others that have embedded code.

[larshp]

user exit referenced = https://docs.abapgit.org/ref-exits.html#custom_serialize_abap_clif

Suggest a new exit SERIALIZE_POSTPROCESS, which can be used to change everything

[AlexandreHT]

Ideally, user exit execution could be restricted to push. (My use case : Code pushed to public git repo should be formatted but code pulled from other repo (eg. abap2xlsx) should be copied as is, in order to avoid false flag diff after import).

[mbtools]

If we only do it on push, it will be hidden to the user as to what happens. I agree with Lars that it should happen at the end of serialize process. Then the results will be visible in repo and diff views.

So I think the exit should go at the end of this method:

https://github.com/abapGit/abapGit/blob/main/src/objects/core/zcl_abapgit_serialize.clas.abap#L331-L357

METHOD files_local.
...
*   Call postprocessing
    li_exit = zcl_abapgit_exit=>get_instance( ).

    li_exit->serialize_postprocess( 
      EXPORTING
        iv_package = iv_package
        ii_log     = ii_log 
      CHANGING
        ct_files   = rt_files ).

ENDMETHOD.

For your (our) purpose, you can then loop over all .abap files in ct_files and pass them through pretty-print with the settings you like.