openapi-types: Fixed OpenAPIV3_1.PathItemObject to accept OpenAPIV3_1… #803
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.
….OperationObject
Problem
In my project, I was trying to construct a OpenAPIV3_1 object as follows
When spreading the object I get the following error: https://pastebin.com/XwXWuavS
Solution
I wouldn't consider myself a savvy typescript guy, but I assume the issue is due to the way the
method
->OperationObject
gets tacked on as a intersection on both V3 and V3_1. This will probably result in typescript interpretingWhich I assume would just boil down to
To solve this, I
Omit
the original mapping ofmethod
toOpenAPIV3.OperationObject
and add it back asmethod
toOpenAPIV3_1.OperationObject
as an intersection at the end. I am not sure if this is the most elegant solution, but it does work.Sidenote: I also noticed a typescript error on
PathsWebhooksComponents
which I think I fixed too