-
Notifications
You must be signed in to change notification settings - Fork 55
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
[SUCO] Add new object type SUCO #662
base: main
Are you sure you want to change the base?
Conversation
|
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.
Hi Daniel, thanks for your AFF. I've added some comments, please have a look. In regard to the failing GitHub Action: We are working on it.
BEGIN OF ty_general_information, | ||
"! <p class="shorttext">Application Default Variant Name</p> | ||
"! Name of the authorization default variant | ||
variant_name TYPE ty_var_name, | ||
"! <p class="shorttext">Language Key for Short Text</p> | ||
"! Language key for short text | ||
language_key TYPE ty_language, | ||
END OF ty_general_information. |
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.
You do not need to save the name of the object and the language key in the interface. The language key is already included in our header as originalLanguage
and the name of the object is provided by our aff framework and is saved in the filename.
I would suggest removing variant_name
and language_key
from ty_general_information
and instead move the contents of ty_leading_application
here.
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 removed the whole type ty_general_information since we would like to keep the section “Leading Application” in the editor. Would that be okay?
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.
We have a naming convention for examples, can you please rename this file to z_aff_example_suco.suco.json
? Please also update the link/name in the README.md
.
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 have uploaded a new example (and README.md) with a name that complies with the convention.
{ | ||
"formatVersion": "1", | ||
"header": { | ||
"description": "Apllication Default Variants", |
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.
"description": "Apllication Default Variants", | |
"description": "Application Default Variants", |
Is it only 1 variant? You wrote VariantS.
Additionally, what does SUCO stand for? Do you think it would make sense to write any reference to what SUCO stands for?
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.
Yes, only one authorization default variant is created or its short text is changed. I changed the texts and inserted one for the whole interface. Now they are more meaningful and singular.
No description provided.