Open shirolk opened 2 months ago
Currently, the tool won't support the literal value, the tool will support the defined types. In the above scenarios is there a particular reason to add a kind as a literal value, if possible to have a kind with ResourceKind
we will map the kind type to the given type.
public type Environment record {
string apiVersion;
ResourceKind kind = RESOURCE_KIND_ENVIRONMENT;
Metadata metadata;
EnvironmentSpec spec;
EnvironmentStatus status?;
};
There are two issues here:
Description: In the types definition that is used for a Ballerina service there is a type which is a union of constants. This type is part of a struct.
When the OpenAPI tool is used to generate the OpenAPI Spec this type is omitted. bal openapi -i service.bal
Later this spec is used to generate a client and as a result the resulting types have a missing field bal openapi -i -o --mode client
Suggested Labels (optional): module/openapi-tools Area/OpenapiToBallerina Area/BallerinaToOpenapi