Skip to content

Refactor error response references in API definition - #249

Closed
bigludo7 wants to merge 1 commit into
mainfrom
fix247
Closed

bigludo7 wants to merge 1 commit into
mainfrom
fix247

Conversation

@bigludo7

@bigludo7 bigludo7 commented Oct 23, 2026 •

Copy link
Copy Markdown
Collaborator

Updated references to error responses in the call forwarding API definition to use centralized definitions from CAMARA_common.yaml.

What type of PR is this?

Add one of the following kinds:

  • correction

What this PR does / why we need it:

Use of common Error schema.

Which issue(s) this PR fixes:

Fixes #246

Special notes for reviewers:

Looking for @tanjadegroot and/or @rartych advice:

  • I haven't use 404 from Common as the API currently provide both NOT_FOUND & IDENTIFIER_NOT_FOUND to avoid introducing a breaking change.
  • Same for 429
  • Last I kept 501 as it is possible for this specific API to not implement both endpoints.

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

Updated references to error responses in the call forwarding API definition to use centralized definitions from CAMARA_common.yaml.
@camara-validation

Copy link
Copy Markdown

CAMARA Validation — PASS

0 errors, 0 warnings, 0 hints | Profile: standard

View full results

@bigludo7 bigludo7 closed this Oct 23, 2026
@bigludo7
bigludo7 deleted the fix247 branch October 23, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use of new Commonalities common error types (through $ref)

1 participant