[Feature Request]: Full support for custom operators in PropertyFilter component
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- react, typescript
- 领域
- frontend
调研方向
Start by reading the PropertyFilter API and the component's operator-dropdown implementation and tests to understand how built-in operators are supplied and rendered. Identify how custom operators are represented in the API and what UI behavior is expected for displaying and selecting them. Done means custom operators defined through the API can be viewed and selected in the UI, with tests covering that behavior.
由索引模型根据 Issue 内容生成。
描述
Description
Description:
While the PropertyFilter component allows specifying a custom operator in the API, there is currently no proper support for displaying custom operators in the UI. Only the built-in operators (<, <=, >, >=, :, !:, =, !=, ^) are shown in the operator dropdown, and custom operators are not visible or selectable by users.
Use case:
We have a requirement to use custom filter operators (for example, "contains any", "matches regex", or domain-specific operators) in the PropertyFilter. Although the API technically allows specifying a custom operator, it is not possible for users to select or view these custom operators in the UI, which limits the usefulness of this feature.
Benefit:
Adding full UI support for custom operators would make the PropertyFilter component much more flexible and allow developers to provide a better filtering experience tailored to their application's needs.
Request:
Please add support for displaying and selecting custom operators in the PropertyFilter UI, so that any operator defined in the API can be used seamlessly by end users.
Code of Conduct
- I agree to follow this project's Code of Conduct
- I checked the current issues for duplicate requests
- 主要语言
- TypeScript
- 星标
- 2.7k
- 派生
- 248
- 平均合并
- 3 天 14 小时
- 30 天内合并 PR
- 83
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
cloudscape-design/components 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
cloudscape-design/components#5184 · 2 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
cloudscape-design/components#5152 · 1 条评论 ·
维护者通常 2 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 15/100
cloudscape-design/components#5149 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 45/100
cloudscape-design/components#5117 · 2 条评论 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
cloudscape-design/components#5106 · 1 条评论 ·
维护者通常 2 天内回复
查看 cloudscape-design/components 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
Graphify-Labs/graphify#4860 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
sveltejs/eslint-plugin-svelte#1615 ·
维护者通常 7 天内回复
-
Parallel reticle_verify opens per-flow leases without the source lease's ignoreHTTPSErrors可能已有人在做 @as992949791 今天认领。 未关闭good first issue help wanted
难度 2/5 1-3 小时 新手友好度 85/100
reticlehq/reticle#2033 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复