-
Notifications
You must be signed in to change notification settings - Fork 66
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
Forbid hashed tables in AFF #386
Conversation
We want to forbid hashed tables, because we do not see any advantage in the AFF. If later there will be use cases, we can remove this limitation.
Wondering, perhaps go as far as having everything SORTED TABLE |
@@ -65,6 +65,8 @@ Each JSON Schema provided in this repository is automatically generated. For thi | |||
|
|||
The ABAP types are self-contained, so it is possible to work on them in any system (e.g., in an SAP BTP, ABAP environment system). | |||
|
|||
Instead of hashed tables, please use sorted tables with a defined key. |
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.
I am wondering whether we should add the information to the sub chapter "Type Mapping" below?
There we could also enhance the table. What do you think?
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.
I enhanced the table. See my newest commit. Please rereview
Let's start/continue discussion in #176 |
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.
I suggest just a minor change. Otherwise, it looks good to me.
Co-authored-by: Michael Schneider <[email protected]>
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, @huber-nicolas . LGTM
We want to forbid hashed tables, because we do not see any advantage in the AFF. If later there will be use cases, we can remove this limitation.
This is a proposal for issue #176