[FOLIO-2917] Develop CI job to ensure API JSON Schema has property descriptions Created: 16/Dec/20 Updated: 19/Jan/21 Resolved: 19/Jan/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | springway | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | DevOps: Sprint 105, DevOps: Sprint 104 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
The current lint-raml CI tool also assesses the JSON schemas to ensure that every property is described. See the "Lint raml schema" stage of the existing buildMvn pipeline. See documentation. Now we need a new tool that assesses JSON Schemas which are associated with either RAML or OpenAPI (OAS) API descriptions. |