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
When upgrading from version 0.4.16 to a higher release we've encountered the following issue: when redefining the same field as in a extended schema, the corresponding "with" method is generated twice: once with a @OverRide, and once without. This means the generated code does not compile. Not that the get and set are generated once, but without an @overrride, although these methods also override base methods.
In 0.4.16, only the "with" method without the Override annotation is generated. We currently use this to restrict and default certain fields in subtypes, this blocks us from upgrading to a higher release.
When upgrading from version 0.4.16 to a higher release we've encountered the following issue: when redefining the same field as in a extended schema, the corresponding "with" method is generated twice: once with a @OverRide, and once without. This means the generated code does not compile. Not that the get and set are generated once, but without an @overrride, although these methods also override base methods.
In 0.4.16, only the "with" method without the Override annotation is generated. We currently use this to restrict and default certain fields in subtypes, this blocks us from upgrading to a higher release.
Full example given the following two schema's:
The following erroneous code gets generated:
The text was updated successfully, but these errors were encountered: