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 resolving linting errors #95

Merged
merged 7 commits into from
Jan 22, 2024

Conversation

rartych
Copy link
Collaborator

@rartych rartych commented Dec 15, 2023

What type of PR is this?

Add one of the following kinds:

  • correction

What this PR does / why we need it:

Proposed changes correct errors detected by:

  • Spectral (OAS linting tool):
    • error parser Mapping key must be a string scalar rather than number
    • oas3-valid-schema-example "example" property type must be string
    • error oas3-valid-media-example "id" property type must be string
  • yamllint:
    • [trailing-spaces] trailing spaces
    • [colons] too many spaces before colon
    • [brackets] too many spaces inside brackets

The version was changed to: 0.5.0-wip

Which issue(s) this PR fixes:

Fixes #94 and #97

Special notes for reviewers:

The output of linting can be seen after expanding "Megalinter" section of workflow results:
https://github.com/rartych/DeviceStatus/actions/runs/7209051170/job/19639229860

Changelog input

Corrections resolving linting errors introduced

Additional documentation

This section can be blank.

docs

Copy link
Collaborator

@bigludo7 bigludo7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -99,7 +99,7 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
version: 0.5.0-rc
version: 0.5.0-wip
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wip?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not familiar with the process, do we have to go back to wip and then make another PR for a release candidate?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the idea is to prepare RC2 after applying changes based on feedback from the latest RC, so the "wip" distinguishes fluid version with ongoing changes from RC.

@hdamker
Copy link
Contributor

hdamker commented Jan 2, 2024

Added #95 as getting fixed by this PR to the description.

@akoshunyadi
Copy link
Collaborator

Correction for getting fixed by: #94 and #97

@akoshunyadi akoshunyadi merged commit e52f5d9 into camaraproject:main Jan 22, 2024
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 this pull request may close these issues.

Corrections needed to resolve linting errors
6 participants