-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ABAP Language Version #184
Conversation
After abapGit/abapGit#6637 - Add grouping to repo settings - Explain name (new) and version (was missing) - Add section on ABAP Language Version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments
I will make a table for the different combinations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @mbtools for the documentation of ABAP language version in abapGit.
Look quite good to me. 👍 I have just added some comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, for the update. I have just some small comments.
I think the setting "Any" has not been supported by the AFF object super class, yet. Currently, it removes the ABAP language version always. |
Co-authored-by: Michael Schneider <[email protected]>
I changed the AFF logic already to remove ALaV only in "ignore mode" This way, the files will be compatible between abapGit and ADT. PS: Doing more testing and bug fixing. |
Ah, good to know. 👍 But one more question: In the documentation it is stated the ABAP LV is also not serialized if the repository is set to a specific version:
I guess we either need to adapt documentation or AFF logic should be remove ABAP LV only if the setting is "Any". What do you think? |
Let's always keep ALaV, for XML and JSON formats, except for the "ignore mode". Then it's clear what you get by just looking at the file. We won't need any mapping when deserializing and can check if the object fits the repo setting. Better? BTW, SAP did not include |
Yes, this is fine for me :) |
Co-authored-by: Michael Schneider <[email protected]>
I added a section about supported object types. This should be good to go |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, there are still some ABAP Language Versions around in the PR, for which I provided SUGGESTIONS. I didn't check the entire files, so maybe there are some left overs there as well.
Thanks for the corrections 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Just one more question regarding supported object types but we can add these later.
👍 |
@larshp you just need to update your review 😉 🙏 |
done, sorry |
Thanks @mbtools for your efforts 👍 |
After #183
Ref abapGit/abapGit#6154
Ref #184