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

Ability to build ARM summary report #421

Open
jianyexi opened this issue Dec 9, 2022 · 0 comments · May be fixed by #422
Open

Ability to build ARM summary report #421

jianyexi opened this issue Dec 9, 2022 · 0 comments · May be fixed by #422

Comments

@jianyexi
Copy link
Contributor

jianyexi commented Dec 9, 2022

To build confidence in the linter automation we need a summary report in the following format that can be the starting place for API reviewers to review the PRs.

For each RT

RPC category #rules #applicable #success #fail
RPC-V1-PUT 22 22 20 2
RPC-V1-PATCH 11 0 0 0
         

we need to investigate how to fix below issues:

  1. the linter output message should include the RT and/or Namespace field , so we may need to update some rules implementation to relate the swagger paths with the rule
  2. Linter should output message for each passed linter rule execution (currently there is no message for passed rules)
    then we can generate a result base on the linter output message
  3. some rules are implemented as only finding the violations of swagger greedily, so they don't have chance to visit all the swagger paths/operations and these rules need to be re-implemented
@jianyexi jianyexi linked a pull request Dec 9, 2022 that will close this issue
@jianyexi jianyexi self-assigned this Dec 12, 2022
@jianyexi jianyexi removed their assignment Mar 13, 2023
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