[Feature Request]: Clarify Label Semantics Operator Components related with Date and DateTime

[jamieleeeeeeee]

Description

Currently the labels of property-filter are directly using the operator value:

label: parsedText.property.propertyLabel + ' ' + value

Could refer to the relevant code implementation here.

While this approach is functional, it can lead to semantic ambiguity. For instance:

• Create after is more intuitive and user-friendly than Create >
• Similarly, Create before is clearer than Create <
• ...

To address this, I propose adding a label generation function to the PropertyFilterOperatorExtended type, such as:

export interface PropertyFilterOperatorExtended<TokenValue> {
  operator: PropertyFilterOperator;
  operatorLabel: (operator: PropertyFilterOperator)=>string
  tokenType?: PropertyFilterTokenType;
  match?: PropertyFilterOperatorMatch<TokenValue>;
  form?: PropertyFilterOperatorForm<TokenValue>;
  format?: PropertyFilterOperatorFormat<TokenValue>;
}

This function could then be executed in the relevant parts of the codebase to dynamically generate more descriptive and user-friendly labels.

I’d be happy to contribute a PR for this feature if needed.
Thank you for considering this suggestion!

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate requests

[jperals]

Hi @jamieleeeeeeee,

Thanks for your suggestion. We don't have plans for this at the moment, but just in case it helps, in the meantime, you can customize the labels that appear below the operator (but not the operator itself) via the i18nStrings, e.g:

{
    operatorLessText: 'before',
    operatorGreaterText: 'after'
}

Note, though, this would modify all instances of these operators, so it would only work as long as you don't use them also for e.g, numeric types.

[yisun-anetac]

Hi @jamieleeeeeeee,

Thanks for your suggestion. We don't have plans for this at the moment, but just in case it helps, in the meantime, you can customize the labels that appear below the operator (but not the operator itself) via the i18nStrings, e.g:

{
    operatorLessText: 'before',
    operatorGreaterText: 'after'
}

Note, though, this would modify all instances of these operators, so it would only work as long as you don't use them also for e.g, numeric types.

Thanks @jperals Will a contribution from us to add such a feature be considered acceptable?

[jperals]

We usually require a relevant number of use cases, and then go through a team-reviewed process, before we add a feature in the system. This is the first time I have seen this particular request, but I made note of it in our internal tracking tools.

[gethinwebster]

@jamieleeeeeeee @yisun-anetac
Discussed this a bit more within the team, and this is something that we would support being added to the system if you'd like to contribute it.