Question: Why does my generated type have a member of type `string option` instead of `ActualType option`?

I generated with the schema: “https://selectapi.datascope.refinitiv.com/RestApi/v1/Authentication/$metadata”.

One of the types that is generated is

type ActionImportRequestTokenPayload =
    { Credentials: Option<string> }

but it should be

type ActionImportRequestTokenPayload =
    { Credentials: Option<DataScopeSelectApiAuthenticationCredentials> }

Looking at the --from-odata-schema output, I see a few cases of anyOf, and I see from the readme section that anyOf is not supported.

Is the current absence of support the reason these types get represented as strings?

[travis-leith]

works, thank you.

[Zaid-Ajaj]

Generating the code becomes a lot more difficult, but will think about it nonetheless. Using type aliases should be easy enough for consumers now