-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
It appears that this should be handled from the way the min/max are calculated in validation, but let's add some thorough unit testing to confirm this is all handled correctly, and fix if not.