[Exposure & Experience Management API] Unused definitions in the specification #38
Assignees
Labels
Comments
|
@maheshc01 please can you take a look? |
|
@Kevsy acknowledging action on the open issue. will push the updates soon. |
maheshc01
added a commit
to maheshc01/EdgeCloud
that referenced
this issue
Apr 17, 2023
updates based on issue camaraproject#38 unused components as mentioned in the issue have been removed. Also updates have been made to use camel case through out the spec for all input and output data.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following shared responses are defined in the "MEC exposure and experience management.yaml" OAS3 specification:
These are not being used/referenced anywhere in the specification.
Please consider preferably using shared response schemas consistently and removing unused components.
Also, I strongly recommend that you consider settling on a consistent Name-Casing convention for schema identifiers, operationIds, type, and attribute names. Some are in lowerCamelCase, some are in snake_case, some are a combination of snake_case and Train-Case, and some are a mixture of the aforementioned.
No doubt a better developer experience if all Camara APIs look and feel consistent.
The text was updated successfully, but these errors were encountered: