[ http://issues.apache.org/jira/browse/BEEHIVE-892?page=all ]
Eddie O'Neil updated BEEHIVE-892:
---------------------------------
Fix Version: TBD
Assign To: (was: Mike Foster)
Fixing some fo the fields -- Zach, unfortunately, (3) isn't going to be an
option once Beehive 1.0 ships. So, if we want to do that, we need to get a
discussion going on the beehive-dev@ list pretty quick. :)
> AnnotationMemberTypes.Decimal.places() should have new default value
> --------------------------------------------------------------------
>
> Key: BEEHIVE-892
> URL: http://issues.apache.org/jira/browse/BEEHIVE-892
> Project: Beehive
> Type: Improvement
> Components: Controls
> Versions: V1
> Reporter: Zach Smith
> Priority: Minor
> Fix For: TBD
>
> Currently AnnotationMemberTypes.Decimal.places() has a default value of '0'
> which in my opinion causes some unecessary work on the part of the Controls
> developer. If a developer sets an AnnotationMemberTypes.Decimal and neglects
> to set places() greater than '0' no decimal places can be used (fails checks
> at compile time). This does not seem intuitive to me given that a Decimal by
> very nature has a decimal place assumed. I propose that one of three things
> be done with places()
> 1. Set it in a way such that it represents unlimited decimal places (limited
> by the system, anyway)
> 2. If the main use case for this is currency consider setting places()
> default value to '2' (however this could be confusing as well and perhaps a
> BasicCurrency type should be created with this value)
> 3. Do away with 'places()' all together and leave it to the developer to
> programatically restrict decimal values.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
