Skip to content

Support numeric range comparison

Choose a tag to compare

View all tags
@halla-ims halla-ims released this 02 Mar 18:33
· 130 commits to master since this release
v1.4-beta
a605be0

Prior to this change, the ranges supported by the algorithms has the requirement that each side was the same length. That is because we were using String comparisons. With upcoming algorithms there is a requirement to support numeric ranges. For example,

"0.1-99999.9"

The solution is that for numeric ranges we will compare as float values (even if integer):

  • If the low and high values ranges are different and are both "numeric", then the value will be compared after converting to a Float (which will work for the Integer type fields as well).
  • Otherwise it will be compared as a String but the strings must be the same length otherwise consider different

For details see #36

Assets 5
Loading