Double Option does not produce distinct results from single Option #1491
Unanswered
firstdorsal
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When using double options to enable setting a field to null there is not distinction in the resulting spec that enables my rust client generator to create this kind of double option code in rust. If you know what to do it is clear in typescript to either set the field to null or omit it but as rust fields can't just be omitted this does not work.
Is this intended and how could it be fixed?
If single options would not be nullable AND not required a distinction could be made.
TypeScript client gen:
When adding
#[schema(nullable = false)]to every single option like here it produces the required or IMO expected results, but i can't add that to every single option.TypeScript client gen:
Beta Was this translation helpful? Give feedback.
All reactions