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
I.e. it forces canFail to true regardless of the underlying Schema and somehow makes the query rendered as nullable even if the corresponsing nullable property is set to false.
If I change canFail to
override def canFail: Boolean = ev.canFail
then the model above becomes rendering as is used to be prior to v2.7.0.
Consider a reproducer:
With Caliban versions up to v2.6.0 (inclusive), the output is the following:
Starting with Caliban v2.7.0 the output changes to this one:
I.e. The
one
query suddenly becomes nullable (even though no changes to the model was made).Works the same for both Scala 2.13 and 3.3.
The text was updated successfully, but these errors were encountered: