-
-
Notifications
You must be signed in to change notification settings - Fork 398
Filtering out primitives from AnyOf #459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
bug
Something isn't working
Comments
Hi @inomn ! |
@js2me hi, cool, thanks! |
Merged
@js2me hi! any estimations on when this could be fixed? |
Is this still being worked on? I'm seeing the same issue and it's preventing me from upgrading. |
eysi09
added a commit
to garden-io/swagger-typescript-api
that referenced
this issue
Mar 16, 2023
This commit adds two fixes needed for Garden's api-types package. First: Ensure that primitve values aren't stripped by setting 'ingoreTypes=[]' see: acacode#459 Second: Ensure union values are printed as T1 | T2 instead of T1 | T2 | (T1 & T2). See acacode#341 and acacode#488
regression in 13.0.2 |
still the case in 13.0.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Good day. In my project we have a case with anyOf string | object
The current implementation of
anyOf
parsing excludes all primitives, but I want to keep them.Any ideas how it could be done?
p.s. on v10 worked well, generated
origin: AddressCreationRequest | string;
Thanks.
The text was updated successfully, but these errors were encountered: