generated from camaraproject/Template_API_Repository
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Convention for file names of API definition #93
Comments
Proposal: rename the file as part of the PR for M4 |
Same than @FabrizioMoggio |
FabrizioMoggio
added a commit
to FabrizioMoggio/CallForwardingSignal
that referenced
this issue
Aug 21, 2024
Closed
Fixed with: #95 |
Fixed with: #101 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
There is currently no guidelines for file names of API definition files in CAMARA.
The initially agreed proposal is to use the convention
api-name.yaml
as a guideline for the API definition file names.Expected behavior
Change the file name to
call-forwarding-signal.yaml
before or as a part of release PR for M4.Alternative solution
Wait for the final guidelines.
Additional context
See the discussion in Commonalities.
The text was updated successfully, but these errors were encountered: