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
Making explicitly-typed methods FieldValue.of{Str,Num,Timestamp,...} has been a mistake, I'm marking them public again. You then should replace FieldValue.ofObj() calls in ExpressionParser back with explicit construction of FieldValues, e.g., a call to FieldValue.ofTimestamp() in parseDateTimeOrNumericValue(). Then you will have a FieldValue that is always a value of expected type inside (or an error if the value does not fit the type).
Implicitly-typed method FieldValue.ofObj() cannot be changed in a way compatible with custom value types. This is because custom value type can have a ValueConverter that accepts any java.lang.Object. In this (very common) case, FieldValue.ofObj(Object, JavaField) will always store the value converted by the JavaField's custom ValueConverter (because it accepts any Object!), as you can see in this bug.
FieldValue.ofObj((long), modelField.getJavaField()) where modelField is UUID field make a str FieldValue.
The text was updated successfully, but these errors were encountered: