Lars Hvam

Serialized directory/folder structure

2

Is defining directory/folder structure in scope? Like in Java, a project typically consists of a folder structure, where each folder contains multiple objects

fyi @absap

zcl_abapgit_res_repo_stage->get

refactor zcl_abapgit_default_auth_info

4

refactor `zcl_abapgit_default_auth_info`, it is part of core abapGit no need to have it implemented twice

some might not be relevant, for reduce line length, see https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abenline_width_guidl.htm regarding naming this is related to #10 and #7 ``` ../ADT_Backend/src/zcl_abapgit_res_repos.clas.abap[54, 11] - Bad attribute name "abapgit_provider" expected "^M._.*$/i"...

the functionallity is part of core abapGit, no need to have it implemented twice

naming

2

suggest prefixing everything with ZABAPGIT_ADT_something(as all the initial code had)


Source is stored in a version management system, so no need for comments regarding old and new code, ```abap *OLD end *NEW start * response->set_status( cl_rest_status_code=>gc_success_accepted ). *NEW end ```

guess some of http://docs.abapgit.org/development/guidelines.html can be reused, eg. pretty printer, but not the downport