Repository navigation
Sync common files from Commonalities r4.4 - #247
1 error, 0 warnings, 20 hints
Profile: standard | Branch: main | Trigger: pr
Annotations
Check failure on line 1 in code/API_definitions/sample-service-subscriptions.yaml
camara-validation / CAMARA Validation
$ref target does not exist
[S-229] '#/components/schemas/Config' does not exist @ 'code/common/CAMARA_event_common.yaml'
Suggestion: The $ref points to a JSON pointer that does not exist in the target file. Check the pointer name against the target's components section — a schema renamed or removed in a newer Commonalities release is the usual cause. Fix the reference in this API definition; do not edit code/common/.
Check notice on line 21 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'identifying-device-from-access-token' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:identifying-device-from-access-token:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 37 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'authorization-and-authentication' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:authorization-and-authentication:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 47 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'additional-error-responses' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:additional-error-responses:BEGIN -->'. | info.description template 'additional-error-responses' has drifted from canonical at paragraph 3.
canonical: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
found: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
Re-copy the BEGIN..END block from 'code/common/info-description-templates.yaml'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 57 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'request-body-strictness' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:request-body-strictness:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 437 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
String has no format/pattern/enum
[S-313] Schema of type string should specify a format, pattern, enum, or const.
Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
Check notice on line 465 in code/API_definitions/sample-implicit-events.yaml
camara-validation / CAMARA Validation
String has no format/pattern/enum
[S-313] Schema of type string should specify a format, pattern, enum, or const.
Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
Check notice on line 12 in code/API_definitions/sample-service-subscriptions.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'authorization-and-authentication' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:authorization-and-authentication:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 22 in code/API_definitions/sample-service-subscriptions.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'additional-error-responses' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:additional-error-responses:BEGIN -->'. | info.description template 'additional-error-responses' has drifted from canonical at paragraph 3.
canonical: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
found: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
Re-copy the BEGIN..END block from 'code/common/info-description-templates.yaml'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 32 in code/API_definitions/sample-service-subscriptions.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'request-body-strictness' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:request-body-strictness:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 17 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'identifying-device-from-access-token' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:identifying-device-from-access-token:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 33 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'authorization-and-authentication' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:authorization-and-authentication:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 43 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'additional-error-responses' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:additional-error-responses:BEGIN -->'. | info.description template 'additional-error-responses' has drifted from canonical at paragraph 3.
canonical: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
found: Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable C...
Re-copy the BEGIN..END block from 'code/common/info-description-templates.yaml'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 53 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
info.description mandatory template content drift
[P-027] info.description template 'request-body-strictness' has no blank line directly after its BEGIN marker. Swagger Editor will not render the following Markdown heading without it. Add one blank line after '<!-- CAMARA:MANDATORY:request-body-strictness:BEGIN -->'.
Suggestion: Re-copy the BEGIN..END block from code/common/info-description-templates.yaml to replace the drifted content; the message identifies the first differing paragraph.
Check notice on line 270 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
String has no format/pattern/enum
[S-313] Schema of type string should specify a format, pattern, enum, or const.
Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
Check notice on line 285 in code/API_definitions/sample-service.yaml
camara-validation / CAMARA Validation
String has no format/pattern/enum
[S-313] Schema of type string should specify a format, pattern, enum, or const.
Suggestion: Acceptable if free-form field or implementation-dependent — no fix needed.
Check notice on line 1 in code/Test_definitions
camara-validation / CAMARA Validation
Missing test definition file for API
[P-006] No .feature test file found for API 'sample-service-subscriptions' in code/Test_definitions/ | No .feature test file found for API 'sample-implicit-events' in code/Test_definitions/
Suggestion: Test files are optional for alpha releases but expected before the first release candidate. On stable (>=1.x) APIs they are required at rc and public release; on initial (0.x) APIs they are strongly recommended. See CAMARA Testing Guidelines for the expected file layout.