You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looking into this a little bit more, the problem comes from the fact that the property factorType is first defined in the UserFactor, and then the example for this same field is defined directly in the child type UserFactorCall. The current implementation does not merge both definitions and the second field ends up being handled as its own independent field with type Object since nothing else is given at this level.
I think that the author wanted to leverage some kind of inheritance, where the field is generally defined in the parent type and then refined (in this case adding an example or a comment) in the child type after the allOff.
I am not sure if this is a valid pattern or not, but it comes from the official okta spec.
The following open api spec is generating code that does not compile.
here is the generated parent class:
and here is the child class:
The text was updated successfully, but these errors were encountered: