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
We have a form that sends it data to the wisdom server.
One of the fields (@FormParameter) sent represents a Date.
Currently, if the date is not provided, wisdom does not even complete the request. This is because the constructor for java.util.Date throws an exception when asked to parse a null String.
I noticed the @DefaultValue annotation, but this only accepts the String that the request "should have" sent. Wouldn't it be cool to recognize @nullable so that we could receive a null Date instead?
The text was updated successfully, but these errors were encountered:
We have a form that sends it data to the wisdom server.
One of the fields (@FormParameter) sent represents a Date.
Currently, if the date is not provided, wisdom does not even complete the request. This is because the constructor for java.util.Date throws an exception when asked to parse a null String.
I noticed the @DefaultValue annotation, but this only accepts the String that the request "should have" sent. Wouldn't it be cool to recognize @nullable so that we could receive a null Date instead?
The text was updated successfully, but these errors were encountered: