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
I've come across a lot of configurations that have optional limits that can be disabled by 0 or -1. This could be represented as a Property<Optional<Integer>> so that the application doesn't need to deal with checking if the property is "disabled".
Would be nice for double, too. Probably not for other types? Esp. considering that for String, the default would just be an empty string. But maybe this can be implemented similar to the existing optional property—it just wraps another property.
The text was updated successfully, but these errors were encountered:
ljacqu
added
good-first-issue
Want to contribute? This label marks well-defined, [relatively] straightforward issues
and removed
good-first-issue
Want to contribute? This label marks well-defined, [relatively] straightforward issues
labels
Aug 29, 2023
I've come across a lot of configurations that have optional limits that can be disabled by
0
or-1
. This could be represented as aProperty<Optional<Integer>>
so that the application doesn't need to deal with checking if the property is "disabled".Would be nice for
double
, too. Probably not for other types? Esp. considering that for String, the default would just be an empty string. But maybe this can be implemented similar to the existing optional property—it just wraps another property.The text was updated successfully, but these errors were encountered: