Remove usages of "@loopback/openapi-v3-types" and deprecate the package #3220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove remaining usage of
@loopback/openapi-v3-types
and deprecate the package.See #301
I decided against upstreaming this helper. The builder in openapi3-ts is adding more empty objects to the spec, I am concerned that by reworking
createEmptyApiSpec
to leverate their builder, we could break existing tests depending on less fields being set in an empty spec.See https://github.com/metadevpro/openapi3-ts/blob/e55fef88e6b9188678528bdf33fee0072033a720/src/dsl/OpenApiBuilder.ts#L14-L35
I decided to move
createEmptyApiSpec
toopenapi-v3
to preserve backwards compatibility for users of ouropenapi-v3
andrest
packages.Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈