-
Notifications
You must be signed in to change notification settings - Fork 2
Introduce GetDecimal() in preference to GetDouble() #109
Copy link
Copy link
Open
Labels
Area: EntityRelates to the core data data structure for modeling topic entities.Relates to the core data data structure for modeling topic entities.Priority: 1Severity 1: MinorStatus 2: ScheduledPlanned for an upcoming release.Planned for an upcoming release.Type: ImprovementImproves the functionality or interface of an existing feature.Improves the functionality or interface of an existing feature.
Milestone
Metadata
Metadata
Assignees
Labels
Area: EntityRelates to the core data data structure for modeling topic entities.Relates to the core data data structure for modeling topic entities.Priority: 1Severity 1: MinorStatus 2: ScheduledPlanned for an upcoming release.Planned for an upcoming release.Type: ImprovementImproves the functionality or interface of an existing feature.Improves the functionality or interface of an existing feature.
When retrieving attributes, we have a number of strongly typed extension methods for retrieving the attributes as specific types. Currently, we have
GetInteger()andGetDouble(). But, in practice, most of the places our clients are usingGetDouble()would be better suited byGetDecimal(). To facilitate this, introduce a newGetDecimal()extension method. We can keep theGetDouble()in case it meets client needs, though we will generally expectGetDecimal()to be preferred.