-
Notifications
You must be signed in to change notification settings - Fork 2
EngSys Desired Goals
Travis Prescott edited this page Nov 18, 2024
·
1 revision
- Systematic way to track suppressions.
Example suppression.yaml:
- tool: rest-api-diff
element: foo/bar/baz
fromVersion: v1
toVersion: v2
-
The existing tool often reports "breaking changes" that are not meaningful to spec authors.
-
Make it easy to run tool on a dev machine
-
Make error messages as clear and "self-serve" as possible, so spec authors can fix their errors without contacting us. Current tool tells you things like "parameter order changed from v1 to v2". OK, but what does that mean, should I fix it or suppress it, etc.
-
If swagger generated from TSP, errors might want to link back to the TSP. Spec authors might not know how their TSP is breaking swagger.