@ceritium
would be interesting a pull request that accept custom attributes for params like 2.0
x-whatever
would be interesting a pull request that accept custom attributes for params like 2.0
x-whatever
?
Hello folks, I'm getting
$ api-spec-converter http://0.0.0.0:3000/explorer/resources --from swagger_1 --to swagger_2 > api-converted.json
[Error: Exception during convertion: SwaggerConverterError: Second argument(apiDeclarations) should be plain object, see release notes.]when running api-spec-converter in a machine but then it's running flawless in another. how should I go about debugging this?
npm update
on both machines
Also check node versions: node --version
and attach spec that you trying to convert
yes it mostly documentation changes
change examples and update README
One thing that I wanted to do in that scope
is to make node module in form object containing
convert function
so require('swagger-converter') => require('swagger-converter').convert
because in future I want to add function that resolve sub-resources
function that return {'/pet.json': 'http://test.com/swagger/pet.json', '/store.json': 'http://test.com/swagger/user.json'}
In any case
1.0.0 will brake API so I think it's good idea to push all breaking changes in it
@mohsen1 What do you think?
1.2 do not support tags but for migrations is useful
I think about doing new realease
1.2.0
What do you think?
protoc-gen-swagger to generate openapiv3 instead of swagger2