-
Notifications
You must be signed in to change notification settings - Fork 57
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
Openapi Generator Fails on allOf #11858
Comments
This issue is stale because it has been open for 5 days with no activity. Remove stale label or this will be closed in 1 day. |
This issue was closed because no activity was received 1 day after it was marked as stale. |
This issue's been twiddling its thumbs for 5 days. Daydreaming, perhaps? Best do something or it's curtains in 1 day. Nudge off the stale label to give it another go. |
This issue's shut up shop. Gave it a day post-stale, then decided, "Enough's enough!" |
What?
When updating to the latest driving-license-book client we get curious messages when running the external-openapi-generator.
The generation does not succeed fully and a lot of types/models are replaced by
unknownBaseType
which then results in our code not compiling due to typescript errors.To reproduce
Have XROAD proxy running.
Possibly related issues
I've found these issues:
They closely mimic the symptoms of this current issue. Curiously I do not find much on this issue for the javascript client.
Solutions
In a recent PR, feat(clients-driving-license-book): Student overview update #11857, I had to manually edit the allOf blocks in the clientConfig since every one of them only had a single reference entry and they could be omitted. Not a great solution but possible in very certain situations. Advantages: not costly in terms of work. Disadvantages are that this doesn't fix anything, really.
Update the openapi generator. Haven't looked deeply into this, but if we go from a major version of 1 to 2, then things start breaking pretty quickly. I tried these following versions as an update but they still had the errors present: [1.0.18-5.0.0-beta2 and 1.0.18-4.3.1]
The text was updated successfully, but these errors were encountered: