FilterBuilder translation of BETWEEN and BETWEEN_INCLUSIVE operators is not working properly / 13.0-p20230315

[eliasbalasis]

FilterBuilder.getCriteria().asString() seems to be translating BETWEEN operator to IBETWEEN and BETWEEN_INCLUSIVE operator to IBETWEEN_INCLUSIVE for all field types, including TEXT.

This is quite unexpected and reproducible on 13.0-p20230315

Is this a bug or are we missing something?

[eliasbalasis]

FYI
The problem is still present in 13.0-p20250430

[Isomorphic]

To clarify, here are the operator labels and their matching operatorIds:

Label	OperatorId
between (inclusive)	iBetweenInclusive
between	iBetween
between (match case)	between
between (inclusive, matchcase)	betweenInclusive

Best Regards
Isomorphic Software

[eliasbalasis]

I am afraid it is possible that we have misunderstood the relationship between "Label" and "OperatorId".
Let me check.

[eliasbalasis]

I can confirm that on 13.0-p20250430 the labels are the same for both the case matching and the case insensitive operators.

Label is "between" for "iBetween" operator
Label is "between (inclusive)" for both "iBetweenInclusive" operator

However:
Label is "between" for "between" operator
Label is "between (inclusive)" for both "betweenInclusive" operator

I am guessing the label is derived from a combination of both the operator and the field type.

[Isomorphic]

Can you clarify what the problem is here?

Bear in mind that, as far as descriptions intended for end users, there is an intentional design decision to keep it simple.

So what's the issue you have here: something is unclear to end users, or criteria descriptions are the same despite different operators, or something else?

Ideally, can you give a specific Criteria where the description seems off?