OpenAPI specification input

[james-blitzm]

This project seems like a good candidate to implement using an OpenAPI-standard specification as an input schema for generation of Singer models.

i.e. Taking the JSON generation one step further to make use of an officially published OpenAPI specification for the target source API.

For example, here is the official OpenAPI specification for the Stripe API v3: https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.yaml

[daigotanaka]

Hi @james-blitzm

This is a great idea and is well-aligned with what I want to build in the major update of tap-rest-api. This project's renewed goal is to create as versatile tap as possible, leveraging standardization such as Open API. The next update is a major rewrite incorporating the enhancement such as

• Pagination by unique keys #5
• OAuth refresh token support #11
• Fully support multiple streams #18
  I will consider your suggestion as one of the top priorities in the release.

Thanks again.

[james-blitzm]

Pagination might be tricky as OpenAPI isn't prescriptive on how this should be implemented. You will need to ensure the developer has the ability to define the pagination model some how.