We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem description Spectral linter applied to device-status.yaml and produces 53 errors (!). Most of them are like:
140:9 error parser Mapping key must be a string scalar rather than number paths./connectivity.post.responses[200]
The response codes (200,...) should be strings
This field MUST be enclosed in quotation marks (for example, "200") for compatibility between JSON and YAML.
Other errors are caused by numeric values of event id in examples that should be quoted as stings:
id
1008:13 error oas3-valid-media-example "id" property type must be string components.examples.ROAMING_STATUS.value.id
Expected behavior Corrections for indicated errors
Alternative solution
Additional context Linting rules are introduced in camaraproject/Commonalities#74 camaraproject/Commonalities#110
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Problem description
Spectral linter applied to device-status.yaml and produces 53 errors (!). Most of them are like:
The response codes (200,...) should be strings
Other errors are caused by numeric values of event
id
in examples that should be quoted as stings:Expected behavior
Corrections for indicated errors
Alternative solution
Additional context
Linting rules are introduced in
camaraproject/Commonalities#74
camaraproject/Commonalities#110
The text was updated successfully, but these errors were encountered: