Fix OpenAPI specs

[provokateurin]

Summary

Some stuff I forgot to commit and small fixes for union types. A future CI will catch the former problems.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[bigcat88]

Does it a good idea to have such large description with an example of the reply?

[provokateurin]

Sorry, I don't understand what you mean. Can you rephrase for me?

[bigcat88]

I am about the part with the description: Output can look like this: ...

[provokateurin]

Ah I see, that description isn't on me though. It's just extracted from the comment of the method.

[julien-nc]

Is it a fix that will have to be done on each future generated OpenAPI specs?

[provokateurin]

If the openapi-extractor is updated and the output is changed, yes. I will add it as a dev dependency and also setup CI. Then the tool will be upgraded by bumping the dependency and thus needing to regenerate the specs. I expect the updates to get less and less in the future as the output gets better and better.