openapi-merge

openapi-merge copied to clipboard

include and exclude based on paths

6

Added configs for include or exclude specification paths based on config provided

RevanthGovindan

Is it possible to add some flag in the config file `openapi-merge.json` which would skip duplicate paths instead of throwing this error? ``` Error merging files: Input 2: The path...

adsiddiqui-equinix

I have several input sources that are protected. Would be nice if user/password or api key could be define in the config file for an inputUrl.

stefan-g

I think it can be nice to use without config files and relying on default sensible parameters. `npx openapi-merge-cli oas/my-app/file.yml ` This is now working but requiring a config file....

cemo

Hi and thanks for the great library / CLI! I've just started using `dispute` with the `alwaysApply` option. While it works great for schema components, the dispute is only effective...

flovouin

Many people define references in OpenAPI files such that those references are not internal to the OpenAPI file. As a result, they expect that when they use the `openapi-merge` library...

robertmassaioli

Add a section in configuration file to define the global title and description of the merge schema

cbeurtheret

Hello, I'm currently exploring the capabilities of OpenAPI and I'm curious if there's a way to merge multiple service Swagger files while selecting only the paths that have a specific...

osimhi213

While working with a specification which has a discriminator with a mapping inside of a oneOf, for example: yaml ``` components: schemas: TestSchema: oneOf: - $ref: '#/components/schemas/TestSchema1' - $ref: '#/components/schemas/TestSchema2'...

davidjlynn

I have an API which when merged with another API results in operationId conflicting. Particularly this occurs when using callbacks, but these have a unique value per API, and I...

davidjlynn