OpenAPI 3.0 Specification Update Collection Suggestions

[Alec-Bailey]

Hello All,

First off, a huge thank you to the maintainers for picking this up where Kong sold out.

A common workflow Kong failed to capture was smart suggestions for updates to a collection derived from OpenAPI specification. At present Insomnium and Postman are the only two real options for an API tooling that support a decent integration with OpenAPI specification. I suspect there are many users like myself who are hurting for this functionality in an open tool without predatory fees.

Whilst greenfield APIs are under active development the base specification can change often and lead to lots of manual updates. Postman has a feature very similar to what I am proposing that helps with this workflow. It's not ideal to have to regenerate the collection and lose request configuration that isn't well captured by the OpenAPI specification.

It seems that some simple drift detection could be implemented as an MVP and expanded upon in the future to include suggested updates and more.

I'd be happy to start work on a PR to implement such a feature. Are others interested in this?
Perhaps @archywillhe may have some thoughts.

Cheers!