Skip to content
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

[SPRV] Sync of AFF in repo with dev #563

Merged
merged 5 commits into from
Nov 10, 2023

Conversation

delucapietro
Copy link
Contributor

No description provided.

delucapietro and others added 2 commits October 18, 2023 13:28
Co-authored-by: abaplint[bot] <24845621+abaplint[bot]@users.noreply.github.com>
Copy link
Contributor

@wurzka wurzka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the AFF. I have a few concerns about the naming of the components. See my comments.

name TYPE c LENGTH 30,
"! <p class="shorttext">Prefix</p>
"! $showAlways
prvname TYPE c LENGTH 30,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We usually suggest to keep the title (shorttext) and the name of the component in sync.
So it would be

Suggested change
prvname TYPE c LENGTH 30,
provider_name TYPE c LENGTH 30,

or even

Suggested change
prvname TYPE c LENGTH 30,
name TYPE c LENGTH 30,

depending on the choice for the title

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will change it to the first suggestion:

The provider name is the name of the provider proxy that is generated during save of the SPRV.
We do not display the SPRV name as it is also visible in the header of the selected object.
Using 'name' as a shorttext could be misleading as it is the name of the dependent provider and not of the selected object.

"! $required
name TYPE c LENGTH 30,
"! <p class="shorttext">Prefix</p>
"! $showAlways
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Field had been required before. Can this field be empty? If yes, showAlways is fine. If not, it should be required.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The namespace is separated into two fields: Base and Suffix.
The namespace itself is mandatory but the base is hardcoded so the user can only enter the suffix in the wizard and we concatenate these fields. The concatenated namespace is required but this is made sure programmatically.
So the field is from my point of view only a "showAlways" for the display view.

"! <p class="shorttext">Namespace</p>
"! Namespace of the service provider
"! $showAlways
prvns TYPE c LENGTH 30,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again here, I suggest not to use an abbreviation

Suggested change
prvns TYPE c LENGTH 30,
namespace TYPE c LENGTH 30,

AFF should be human readable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to namespace

@delucapietro
Copy link
Contributor Author

Suggestions fixed with pull request #566

Copy link
Contributor

@schneidermic0 schneidermic0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can still change this object type incompatible. It hasn't been available, yet.

Looks good to me. Thanks @delucapietro for the update.

@schneidermic0 schneidermic0 merged commit 89a1440 into SAP:main Nov 10, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants