Skip to content

fixed lint.sh, allowed 'all' to be passed to lint.sh to lint everything, not just changed files, and updated readme accordingly#9

Open
billy-kimble-sp wants to merge 2 commits intomainfrom
lint_sh
Open

fixed lint.sh, allowed 'all' to be passed to lint.sh to lint everything, not just changed files, and updated readme accordingly#9
billy-kimble-sp wants to merge 2 commits intomainfrom
lint_sh

Conversation

@billy-kimble-sp
Copy link
Collaborator

lint.sh was hardcoded to look at master but api-specs uses main , so it was failing to run lint on the changed files. I fixed that. While in there, I also realized there was no ability to run lint on everything regardless of it was changed, so I added that ability via an argument too.

…ng, not just changed files, and updated readme accordingly
then
files=$(find . -name "*.yaml")
else
files=$(git diff --name-only HEAD main)
Copy link
Contributor

Choose a reason for hiding this comment

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

Are you linting agains cloud-api-client-commons? I don't see a main branch on our internal spec repo, just master.

Comment on lines -39 to -54
path-parameters-must-have-valid-formats-for-numbers-and-integers:
message: "{{error}}: https://sailpoint-oss.github.io/sailpoint-api-guidelines/#171"
given: $.[*].parameters[?(@.$ref == null)]
severity: error
then:
function: path-parameter-integer-number-formats
functionOptions:
rule: 171
path-summary-length:
message: "{{error}}: https://sailpoint-oss.github.io/sailpoint-api-guidelines/#305"
given: $[*].summary
severity: warn
then:
function: word-count
functionOptions:
maxWordCount: 5
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are all of these path and schema rules commented out?

@colin-mckibben-sp
Copy link
Contributor

@billy-kimble-sp Thank you for your contribution, and sorry it took so long to get back to you. I want to get your changes merged, but I'll need you to resolve the conflicts and comments first.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

3 participants