Skip to content
New issue

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

Corrections needed to resolve linting errors #94

Closed
rartych opened this issue Dec 15, 2023 · 0 comments · Fixed by #95
Closed

Corrections needed to resolve linting errors #94

rartych opened this issue Dec 15, 2023 · 0 comments · Fixed by #95

Comments

@rartych
Copy link
Collaborator

rartych commented Dec 15, 2023

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:

  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

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 a pull request may close this issue.

1 participant