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:
- 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
- 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
- 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
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
we need to investigate how to fix below issues:
then we can generate a result base on the linter output message