abapGit / abapGit/docs.abapgit.org
Feedback to abap-language-version.md
Nobody has claimed this yet.
- Dominant language
- ABAP
- Stars
- 35
- Forks
- 46
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with abap-language-version.md, especially the “Any ABAP Language Version” section and its Import subsection. Clarify whether the requested outcome is a documentation correction or a change to import behavior, then record the agreed handling of enforced “ABAP for Cloud Development” versions and define how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100