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
Both seems to have the same purpose, only with separate terms. I think we need to just merge it into one, but we might want to discuss this further before any changes.
Thoughs?
The text was updated successfully, but these errors were encountered:
It did cross my mind to use the same Comparator for both number and date comparison but imo separating them into two comparators with different terms (i.e. GREATER_THAN and AFTER) provide more clarity for the context in which they are used for the users
Both have the same functionality:
Comparator.LT == DateHelper.TimeComparator.BEFORE
Comparator.LTE == DateHelper.TimeComparator.BEFORE_OR_EQUAL_TO
Comparator.EQ == DateHelper.TimeComparator.EQUAL_TO
Comparator.GT == DateHelper.TimeComparator.AFTER
Comparator.GTE == DateHelper.TimeComparator.AFTER_OR_EQUAL_TO
We can merge the two classes of course, but imo is(date1, BEFORE, date2) is easier to read and understand contextually than is(date1, LESS_THAN, date2) or is(date1, LT, date2).
Both seems to have the same purpose, only with separate terms. I think we need to just merge it into one, but we might want to discuss this further before any changes.
Thoughs?
The text was updated successfully, but these errors were encountered: