Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/OpenAPITools/openapi-generator/issues/10352 below:

[BUG] [Haskell-http-client] `anyOf` generates bad type names · Issue #10352 · OpenAPITools/openapi-generator · GitHub

• Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator (example)?
• Have you tested with the latest master to confirm the issue still exists?
• Have you searched for related issues/PRs?
• What's the actual output vs expected output?
• [Optional] Sponsorship to speed up the bug fix or feature request (example)

The haskell-http-client generator doesn't handle the use of anyOf in an OpenAPI v3 spec properly. Trying to use anyOf will lead to malformed code which uses type name that don't exist, and will fail to compile.

Found on latest master: 2239ca36fdcedd865a3d9ccd3381f5031cdf8dbe.

Gist here: https://gist.github.com/ivanbakel/cbf8a00b30cbe71ca0fe86a5c9c44a18

I ran

generate -i ... -o ... -g haskell-http-client

with the above file (in the gist).

1. Generate the Haskell HTTP client code from the above file.
2. Try to compile it.
3. Get an error that AnyOfFooBar is not a type

May be related to #2968, which is a similar issue where a Haskell-based code generator produces malformed type names when using anyOf.

It looks like AnyOf simply isn't supported in the haskell-http-client schema at the moment. That would be very hard to fix, but ideally the above case, where there's an anyOf with a single child, could be simplified to just use that child type. So AnyOfFooBar in the above generated code would become just FooBar, since that's the only type in the anyOf.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4