Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.0.1-incubating-core-SNAPSHOT
-
None
-
None
Description
convertNumber error message misleading when integerOnly is true.
If I enter 1.1 it says "Not a number". 1.1 is a number, just not an integer,
so the user doesn't know how to fix this.
Partial workaround is to set messageDetailConvertNumber for the detail. Still
see "Not a Number" for the summary.
Ideally when integerOnly set then the default messages would match the
integerConverter messages.