Repository navigation
Align responses with commonalities r4.4 - #153
GillesInnov35 wants to merge 8 commits into
Conversation
Updated the Verified Caller API specification to include detailed descriptions, parameters, and response examples for the pre-announcement functionality.
Updated the Verified Caller API specification to include detailed descriptions of functionality, parameters, and error handling.
CAMARA Validation — PASS (with warnings)0 errors, 3 warnings, 8 hints | Profile: standard |
|
@ALL,if we take a look at what CAMARA_event_common.yaml, new errors content are included. What I understand is that if we'd like to be fully aligned with CAMARA_event_common.yaml by updating |
|
hello @GillesInnov35 , I undertand you are only asking about the errors for the notifications? |
Oh yes you're right. Ok I'm going to include reference for notification errors. Thanks |
Hi @GillesInnov35 , are you going to further modify this pr? Thank you |
@alpaycetin74 , yes I’ll do it quickly |
alpaycetin74
left a comment
There was a problem hiding this comment.
Could you please have a look at the linter warnings @GillesInnov35 ? Thank you.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Align responses section with commonalities r4.4 according
CAMARA_common.yaml
- DEPRECATED error responses - The Generic* responses are DEPRECATED as of Commonalities 0.9.0
- normalize naming of local errors according to CAMARA_common.yaml
CAMARA_event_common.yaml
sample-service.yaml
- include locally HTTP-50x errors and specific definitions
Which issue(s) this PR fixes:
Fixes #152