f04be48f61
* [WEB-5804] refactor: decouple filter value types from filter configurations Remove value type constraints from filter configurations to support operator-specific value types. Different operators can accept different value types for the same filter property, so value types should be determined at the operator level rather than the filter level. - Remove generic value type parameter from TFilterConfig - Update TOperatorConfigMap to accept union of all value types - Simplify filter config factory signatures across all filter types - Add forceUpdate parameter to updateConditionValue method * refactor: remove filter value type constraints from filter configurations Eliminate the generic value type parameter from filter configurations to allow for operator-specific value types. This change enhances flexibility by enabling different operators to accept various value types for the same filter property. - Updated TFilterConfig and related interfaces to remove value type constraints - Adjusted filter configuration methods and types accordingly - Refactored date operator support to align with the new structure |
||
|---|---|---|
| .. | ||
| app-rail | ||
| editor | ||
| pages | ||
| rich-filters | ||
| store | ||
| work-item-filters | ||
| use-additional-editor-mention.tsx | ||
| use-additional-favorite-item-details.ts | ||
| use-bulk-operation-status.ts | ||
| use-debounced-duplicate-issues.tsx | ||
| use-editor-flagging.ts | ||
| use-file-size.ts | ||
| use-issue-embed.tsx | ||
| use-issue-properties.tsx | ||
| use-notification-preview.tsx | ||
| use-page-flag.ts | ||
| use-timeline-chart.ts | ||
| use-workspace-issue-properties-extended.tsx | ||