Nullable fields generating broken field implementations

[craiglabenz]

While running the User / Post example in the README, I've encountered a problem with the initial generated code.

It seems that nullable fields (e.g., name String?) generate the following Dart code:

final _i2.PrismaNullable<_i2.PrismaUnion<StringNullableWithAggregatesFilter, String, _i2.PrismaNull>> name;

Which breaks, because the class definition for PrismaUnion accepts 2 type parameters

class PrismaUnion<T0, T1> {}

Yet we've provided three

PrismaUnion<StringNullableWithAggregatesFilter, String, _i2.PrismaNull>

[medz]

I checkedout a new branch to reproduce and will fix this.

[medz]

For this bug fix, I don't think the generated input object type should be PrismaUnion wrapped, just StringNullableWithAggregatesFilter.

However this is a breaking change and a separate test has been created for this issue.

It will be fixed in the 2.2.0 release after waiting for the CI to be added.

[medz]