Project: datamanagement
Issue DM-3638: RangeField mis-handles max < min
RangeField contains the following bit of code to handle the case that max < min: {code} if min is not None and max is not None and min > max: swap(min, max) {code} This is broken because there is no swap function and if there was it could not work in-place like this. However, rather than replace this with the standard {{min, max = max, min}} I suggest we raise an exception. If max < min then this probably indicates some kind of error or sloppiness that should not be silently ignored. If we insist on swapping the values then at least we should print a warning. The fact that this bug has never been reported strongly suggests that we never do set min > max and thus that an exception will be fine.
Story points: 1