We allow custom types in Slice1 with the caveat that (per the docs):
If you use this custom type as an optional (with a ? suffix) outside of a tag context, you also need to supply methods to encode/decode a nullable value of this type. With our example:
But the generated code doesn't honor this.
It will always use the nullable function, even in tagged contexts.
We allow custom types in Slice1 with the caveat that (per the docs):
But the generated code doesn't honor this. It will always use the nullable function, even in tagged contexts.
Example:
This generates:
Note that we call 'EncodeNullable' and 'DecodeNullable' when we should be using the non-nullable versions.