Namespaces

[larshp]

Hi,
The repository contains some objects with quite generic names, eg:
FUGR ZREST
TABL ZREGISTER
DOMA ZCLASSNAME
DTEL ZCHAR75
DTEL ZORIGINAL
DTEL ZURI
DTEL ZUNAME
For these, there is a theoretical chance that the customer already has an object with identical names in their system.

I recommend prefixing objects to lower the risk, eg.
FUGR Z_AZURE_REST
TABL Z_AZURE_REGISTER
DOMA Z_AZURE_CLASSNAME
DTEL Z_AZURE_CHAR75
DTEL Z_AZURE_ORIGINAL
DTEL Z_AZURE_URI
DTEL Z_AZURE_UNAME
or something similar

[krdash]

Thanks for the feedback. We are working on this.

[krdash]

@larshp -
We are looking into your suggestion for getting a unique Namespace.
I have one query on ABAPGit to understand whether ABAPGit would show any object overwriting warnings while doing the pull or clone from the repository to SAP system. Thanks

[larshp]

unique namespace: in my opinion it is easier just to prefix

overwrite: yes it shows warnings if the objects it tries to overwrite are outside of the expected package hierarchy(main repo package)

[bigld]

@krdash So, is ZxxADFxx the actual prefix Namespace (e.g. ZCL_ADF_..., ZADF_S_STRUC...)?
Should we move ZREST to ZADF one by one?

[atarigui]

What is the status on this? It seems to me that the correct way to do it is to introduce a proper name space, instead of customer namespace Z...
For instance /AZURE/
Everything else will cause problems at some point...

[bigld]

Namespace must be Z or Y!
For reserved Namespaces like /AZURE/ one needs special key (producer/repair) to create objects in this namespace!

[atarigui]

The problem is that this comes with name conflicts, which can not be prevented as long as the objects are in Z (customer) name space. ref other issue #41 . Maybe the repair key could be shared (similar to DEMO objects in SAP)? See for instance this

[vikasbansal2022]

Thanks @larshp for the feedback,

We are working towards unified namespace for the next release will keep you posted.

Regards,
Vikas

[larshp]

cool

one tip, you can setup abaplint to automatically check the objects have the preferred prefix, example at https://github.com/abapGit/abapGit/blob/main/abaplint.json#L335-L339