First off, I wish I know FP better so I could contribute more here, but this stuff rea

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Issues with Component Responses about openapi-io-ts HOT 1 OPEN

fredx87 commented on August 22, 2024

Issues with Component Responses

from openapi-io-ts.

Comments (1)

Fredx87 commented on August 22, 2024

Hi @aphex, thank you for helping test the library. As mentioned in the README there are still some bugs and missing things around. I am working on some refactorings and I am planning to do a new release soon.

Regarding your issues:

This is probably a typo, I will check it
It is possible to use import type, but I am refactoring the generated code for operations, and probably TaskEither will not be imported in these files anymore
The handling of error responses is not very well implemented and tested in this version, for the first iteration I looked more at the successful responses. For this reason, it is possible that in the generated code there are some references to missing things.
The reason for having things like { _tag: "JsonResponse", decoder: Error401Schema } for handling errors is that is possible that an error is not a JSON but a string, or an empty response (or maybe also a binary file... I guess nobody is doing that but it is possible). So the runtime will need to know the response type to decode it.
At the moment the decoding of errors in the runtime is not implemented (it will just return an ApiError with the Response inside). The idea is that you will be able to have an ApiError<T>, where <T> in your case will be schemas.Error.