[Feature Request]: Implement label to the filter-state

[gogonzo]

part of #48 should rather follow #129

Feature description

Label should be a reactiveValue which:

1. by default it observes private$selected (filter values) and label should be:
   • for numeric, dates and datetime {dataname}.{varname}: {min(selected)}-{max(selected)}
   • for characters and factors {dataname}{varname}: {paste(selected, collapse = ",")}. Length of the label should be limited to X characters. We can figure value of X during the implementation
2. It should observe also textInput where user can specify the label. After label is applied - it no longer follows reactive selection (1)
3. Please add protection to not have a duplicated label.

[donyunardi]

Due to our de#date, I feel that we can close this issue.

In summary, the current state of the filter card includes two rows: the first row displays the column name and label (if applicable), while the second row shows the selected values, which change dynamically based on user input.

@gogonzo thoughts?

[gogonzo]

I think this is still needed but the result should be discussed. Maybe users should be allowed to set values of the filter, name it accordingly (e.g. "adult") to avoid showing numbers which might not say anything. I'd like to discuss this at some point

[donyunardi]

Thanks, we can discuss this more.
Priority-wise, let's address this at the next increment.

[donyunardi]

Let's start the discussion.

@lcd2yyz
Could you please define the expectation of the filter-state label from user's perspective?

• How the label should look based on current design?
• What's the behavior of the label?
• Should value be shown under the label or should it tooltips, etc?
• I think filter-state label is motivated by citril/citril.metadata, should we gather user requirement from that team too?

[lcd2yyz]

This is closely related to #220 , let's tackle these together in a discussion session.

[donyunardi]

Per discussion with @lcd2yyz, this is no longer needed in favor of filter expression.