[x] Make sure multiline Rib works in yaml (just to validate prioritizing this work)
[x] REST-API support for importing open-api-format-api-definition for both yaml and json using content-type negotiation. yaml content-type in header will support yaml import.
[x] golem-CLI support for importing open-api-format-api-definition for both yaml and json.
[x] REST-API Native API definition format, supporting both yaml and json. Here, make sure to support output yaml and json formats. Probably output can be a concern of just clients instead of lots of changes required in client generation side to support Accept headers (similar to content type header)
[x] golem-cli support for Native API definition format in both yaml and json format. Specify --def-format yaml if importing yaml spec through golem-cli. json is by default to keep backward compatibility.
[x] FYI: CLI tests succeed only if we strongly distinguish yaml and json parsing, instead of trying to magically parse anything that user passes without any hint of what's the format of file (hints being content-type for REST API, and --def-format for CLI), and also error reporting becomes clear.
OpenAPI in yaml format with multi-line Rib that works
TODO
yaml
andjson
using content-type negotiation. yaml content-type in header will support yaml import.yaml
andjson
.--def-format yaml
if importing yaml spec through golem-cli.json
is by default to keep backward compatibility.OpenAPI in yaml format with multi-line Rib that works