fix: resolve CAMARA validation warnings - #229
Merged
Merged
Conversation
- P-026: Add mandatory info.description templates with BEGIN/END markers (authorization-and-authentication, additional-error-responses, request-body-strictness, identifying-phone-number-from-access-token) - S-309/S-031: Add maxItems: 5 and description to CallForwardingSignal array items - S-011/S-310/S-311/S-312: Replace local XCorrelator, ErrorInfo and PhoneNumber schemas with \ to ../common/CAMARA_common.yaml - S-021: Convert tag names to Title Case - P-032: Delete obsolete API Readiness Checklist file
rartych
requested review from
FabrizioMoggio,
bigludo7 and
chinaunicomyangfan
as code owners
July 24, 2026 14:12
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Fixes all warnings reported by the CAMARA Validation workflow (advisory profile):
info.descriptiontemplates with properBEGIN/ENDmarkers:authorization-and-authentication,additional-error-responses,request-body-strictness, andidentifying-phone-number-from-access-tokenmaxItems: 5anddescriptiontoCallForwardingSignalarray itemsXCorrelator,ErrorInfo, andPhoneNumberschemas with$refto../common/CAMARA_common.yaml, which already provides all required constraints (format,minimum,maximum,maxLength,description)Unconditional Call Forwarding Information Retrieval,Call Forwarding Information Retrieval)call-forwarding-signal-API-Readiness-Checklist.mdfileWhich issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
XCorrelator,ErrorInfo, andPhoneNumberschemas are now referenced directly fromcode/common/CAMARA_common.yamlinstead of being redefined locally, ensuring alignment with Commonalities r4.3.Changelog input