generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Missing guideline for file names of API definition files - mixed use of snake_case and kebab-case #284
Labels
Comments
From TEF side we are agree with this issue and its resolution:
|
From Orange perspective agree as well on the issue & resolution. |
This was referenced Aug 20, 2024
This was referenced Aug 22, 2024
This was referenced Nov 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem description
There is currently no guidelines for file names of API definition files in CAMARA.
The release candidates for Fall24 are all using the API name together with .yaml, but a mix of snake_case and kebab-case. For consistency in the meta-release and to be prepared for future automation with scripts this must be harmonized.
The API Design Guideline has already a definition of
api-name
in chapter 11.6.1 Scope Naming:Within the path the api name must be in kebab-case. The proposal is therefore to use the convention
api-name.yaml
as a guideline for the API definition file names.Possible evolution
The changes might shouldn't be done in Commonalities 0.4.0 to avoid broken links, but a decision for the format should be taken, so that API Sub Project voluntary can do the change already for the Fall24 release, e.g. as part of their release PR for M4.
Alternative solution
Additional context
The majority of APIs in the Fall24 meta-release are using already the convention api-name.yaml.
snake_case is currently used in five repositories, where SimSwap is mixing both variants:
The text was updated successfully, but these errors were encountered: