Skip to content

Corrections needed to resolve linting errors #94

@rartych

Description

@rartych

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions