-
Notifications
You must be signed in to change notification settings - Fork 30
Clarification meaning of {{API_NAME}}.{{SPECIFIC_CODE}} #541
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
Clarification meaning of {{API_NAME}}.{{SPECIFIC_CODE}} #541
Conversation
…o clarification_meaning_API_NAME.SPECIFIC_CODE
patrice-conil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
tlohmar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
|
In CAMARA_common.yaml we have But in This raises linting errors - I did the exercise to check if CAMARA_common.yaml is not propagating linting problems in API definitions. Here it is not the case because the pleaceholders should be replaced in API definitions, but to avoid this error even when linting CAMARA_common.yaml I propose to change The same for: |
|
Yes, LGTM |
Co-authored-by: Rafal Artych <121048129+rartych@users.noreply.github.com>
…o clarification_meaning_API_NAME.SPECIFIC_CODE
|
Have proposed in commit b9f4c2e Also fine if you think is better to set message: Message for specific code (@rartych, @patrice-conil, @tlohmar). |
|
Ready for review |
rartych
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jlurien
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
patrice-conil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What type of PR is this?
What this PR does / why we need it:
This PR deals with some clarification required in order to state clearly how to define an specific API exception under the {{API_NAME}}.{{SPECIFIC_CODE}} scheme
Which issue(s) this PR fixes:
Fixes #538
Does this PR introduce a breaking change?
Special notes for reviewers:
N/A
Changelog input
Additional documentation
N/A