Api spec fixes from linter rules #137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PedroDiez
requested review from
ToshiWakayama-KDDI and
bigludo7
as code owners
|
Going to close and generate a new one considering the linter rules output |
|
Have make some tests but seems there is no way currently to modify "release" branch as current config |
rartych
approved these changes
Jan 30, 2024
|
I am merging this PR and going to trigger linter rules again to check the result |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
PR to fix some API spec format considerations from linter rules:
PR created over release-0.2.0 branch in order to incorporate to it before merging
Which issue(s) this PR fixes:
Fixes #126