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

Interface file definitions naming #128

Closed
larshp opened this issue Jul 19, 2021 · 5 comments · Fixed by #154
Closed

Interface file definitions naming #128

larshp opened this issue Jul 19, 2021 · 5 comments · Fixed by #154
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@larshp
Copy link
Collaborator

larshp commented Jul 19, 2021

we currently have:

zif_oo_aff_intf_v1.intf.abap
zif_atc_aff_chkc_v1.intf.abap

INTF and CHKC are the TADIR R3TR names, which are guaranteed to be unique, I suggest leaving out the "_oo" and "_atc" parts

@schneidermic0
Copy link
Contributor

We have to consider interface names for R3TR objects and most probably LIMU objects.

Furthermore, we have to define the naming for reuse interfaces (like the one for classes and interfaces; see #143).

@schneidermic0
Copy link
Contributor

To rename the interface names stored in this repostitory, a issue #151 was opened.

Therefore, can we close this one? The documentation about the interface name was add in #146.

The name of the interface follows the pattern zif_aff_<object_type>_v<version_number>.

@wurzka
Copy link
Contributor

wurzka commented Aug 4, 2021

Yes, we can close this one

@larshp
Copy link
Collaborator Author

larshp commented Aug 4, 2021

agree, its dococumented

and renaming is #151

@larshp larshp closed this as completed Aug 4, 2021
@schneidermic0 schneidermic0 added the documentation Improvements or additions to documentation label Aug 5, 2021
@schneidermic0
Copy link
Contributor

Specification for the interface names of R3TR objects is available.

Unfortunately, it is still unclear how interface names for LIMU objects shall be handled. See comments in #153.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants