Feedback to abap-language-version.md

[anfisc]

Section # Any ABAP Language Version

Import
When deserializing objects, abapGit will set the ABAP language version according to the metadata of each object.

--> In systems that use software components which enforce the use of the language version "ABAP for Cloud Development" the import tool should not try to set the language version to "ABAP standard" since it will not be possible to activate the object even if the source code might be compatible.
It is very cumbersome to change the ABAP language version for several objects since no mass change support is available for this in ADT. So it should be tried to set the language version to the version that is enforced or the import should be blocked to prevent lots of objects to be created that cannot be activated by definition.

[larshp]

@anfisc this looks like a suggestion to update the documentation? pull request are welcome

[mbtools]

I know, it's complicated but I have spent already weeks on the topic without getting paid for it. This now has low prio for me. Sorry.

PS: There's a "Sponsor me" button if SAP needs help 😉

[anfisc]

@anfisc this looks like a suggestion to update the documentation? pull request are welcome

I have updated my issue such that moved the suggested changes to a pull request.
The proposal for the behavior of ZABAPGIT not to import stuff where it "knows" that this will break I have left as an issue.