You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Report thresholds for metrics for example usually only have the constraint that they must be positive. It makes no sense to artificially restrict that, and it obliges us to take an arbitrary decision ("is 2000 enough? should I add a zero?"). We could add some methods mustBeAbove and mustBeBelow to the property builders and implement some logic in the NumericPropertyModule to have unbounded intervals.
When defining a property programmatically, one can use NumericConstraint.positive()
But when defining a property in XML, you always have to provide min and max:
adangel
changed the title
[core] Allow numeric properties to be within an unbounded range
[core] Allow numeric properties in XML to be within an unbounded range
Jan 11, 2023
Report thresholds for metrics for example usually only have the constraint that they must be positive. It makes no sense to artificially restrict that, and it obliges us to take an arbitrary decision ("is 2000 enough? should I add a zero?"). We could add some methods
mustBeAbove
andmustBeBelow
to the property builders and implement some logic in the NumericPropertyModule to have unbounded intervals.NumericConstraint.positive()
min
andmax
:The text was updated successfully, but these errors were encountered: