Maxim

feat: introduce problem severity levels

6

Issues with API definitions might be of different criticality. Some issues are of informative character and some are very critical. To differentiate we can introduce problem `severity` field. It can...

feat: implement a check for AIP-193 (#911)

7

Signed-off-by: Maxim Tschumak

google.aip.dev/193

[EPIC] Rule Sets

12

This Epic proposes a concept of Rule Sets. This is a grouping mechanism for rule checks and aims to make Zally implementation more general and allow usage beyond Zalando. **As**...

Improve UseSpecificHttpStatusCodes Rule

3

Check implementation should be aligned more to Guideline Rule [150](http://zalando.github.io/restful-api-guidelines/#150). **Acceptance Criteria** * List of standardized HTTP response codes is compiled (research needed) * Both aspects are covered: 1. Response...

[Rule Sets] 3. Package Discovery

8

## Epic: [Rule Sets](https://github.com/zalando-incubator/zally/issues/551) **Acceptance Criteria** - "Zalando API Guidelines" and "Zally" Rule Sets are split up - Server discovers packages from a configured directory - Build is adjusted to...

## Epic: [Rule Sets](https://github.com/zalando-incubator/zally/issues/551) **Acceptance Criteria** - Developer manual (how to design and implement a rule set) - Administrator manual (how to operate zally installations) - User manual (how to...

## Epic: [Rule Sets](https://github.com/zalando-incubator/zally/issues/551) **Acceptance Criteria** - Statistics include Rule Set - Statistics include Rule Id

`x-zally-ignore`: explanation must be mandatory for each ignored rule

1

Currently, `x-zally-ignore` extension accepts a set of `RuleId`s to be ignored. This is a great feature, but we have to assure the correct usage of it. Let's begin with understanding...