Update API generation with openapi-generator (kotlin/multiplatform instead of Kotlin/jvm) about moko-network HOT 6 OPEN

in our usecases we not read response headers yet and do status code checks only in ErrorFeature (if status code not successful then this feature try create exception for this case).
i think it will be good if we add HttpResponse<Model> case in generation, in addition to already exists methods

from moko-network.

@ATchernov the problem is that you still support only 1.3.50 version of kotlin. You need to update the kotlin-multiplatform generator to address the new kotlin versions and maintain that in a faster way [-;

from moko-network.

@shadowsheep1 moko-network use 1.3.70, what do you mean about 1.3.50?

from moko-network.

Hey @ATchernov didn't see you're a moko-network contrib, thinking you were from openapi plugin, sorry. Moko is great 'casue it follows tight kotlin version releases, while the openapi client gen is stuck on 1.3.50.
https://github.com/OpenAPITools/openapi-generator/blob/master/docs/generators/kotlin.md
OpenAPITools/openapi-generator#5346

At a first look, you differ from the kotlin-multiplatform version

--library multiplatform

java -jar openapi-generator-cli-4.2.2.jar generate -g kotlin -p packageName=it.shadowsheep.mpp.app.client --library multiplatform --additional-properties nonPublicApi=true -i openapi.yaml -o open_mpp

of openapi-client client gen because you return the Model and not the HttpResponse<Model> of the model.

This way how do you propagate http response status code and headers? This info should be useful.

/cc @Alex009

from moko-network.

required usecase - reading of headers in response

from moko-network.

Another use case is that we have response status code with a deeper meaning (read custom meaning) so that we act in some way when we have a particular status code.

from moko-network.