Hello,
Our team has been discussing this rule that makes duster to fail when we declare a nullable type of an default null type.
We believe the second form is the correct, since the type is a nullable user, however we understand that there are cases that the first form makes sense, but it is not a good architecture
Is there any reason why duster defaults to the first form, and is there any way to force the second one?
Hello, Our team has been discussing this rule that makes duster to fail when we declare a nullable type of an default null type.
We believe the second form is the correct, since the type is a nullable user, however we understand that there are cases that the first form makes sense, but it is not a good architecture
Is there any reason why duster defaults to the first form, and is there any way to force the second one?
Thanks!