Make UI consistent regarding when to clear input validation errors
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
调研方向
Compare validation-error behavior in the and , then locate the style guide and all other places where input validation errors are shown. First resolve the project-wide rule for clearing errors; done means the rule is documented and consistently applied across those locations.
由索引模型根据 Issue 内容生成。
描述
We currently don’t follow a consistent pattern in regards to clearing validation errors:
- In the
<security-dialog>, if you enter too short a password and try to submit the form, the validation error is hidden once you start changing one of the input fields (i.e., once you start typing). - In the
<change-hostname-dialog>, if you enter a malformed hostname such as*&!^@^#*(, the validation error stays until you re-submit with another input value.
Good points can be made for either way:
- By clearing the validation error after the user starts doing something, we acknowledge that the problem now might have gone away, and the user might feel more encouraged to re-try their submission.
- By leaving the validation until re-submission, the user is able to study the error text, in order to ensure that they address the issue properly. That’s especially helpful if the error message contains more comprehensive information, such as the allowed characters for a valid hostname.
A potential third (middleground) option could be to add some sort of “dismiss” functionality (e.g., an × button in the upper right corner of the inline message box). That way, the error box would persist by default, but the user could explicitly make it go away.
What we should do is this:
- Come up with and decide on an explicit rule how we go about clearing validation errors. This should be documented in the style guide.
- Roll out the new rule to all places where input validation errors are shown.
- 主要语言
- Python
- 星标
- 3.5k
- 派生
- 292
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
tiny-pilot/tinypilot 的其他 Issue
-
bug medium
难度 2/5 1-3 小时 新手友好度 62/100
tiny-pilot/tinypilot#1419 ·
-
bug
难度 5/5 一周以上 新手友好度 15/100
tiny-pilot/tinypilot#1961 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
tiny-pilot/tinypilot#1929 · 3 条评论 ·
-
bug
难度 3/5 1-2 天 新手友好度 35/100
tiny-pilot/tinypilot#1899 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
tiny-pilot/tinypilot#1896 ·
查看 tiny-pilot/tinypilot 的全部 Issue
相似的 Issue
-
Deferred from #1869: Complete the companion pytest guardrail update noted in the PR description...未关闭
难度 1/5 1 小时以内 新手友好度 95/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
NousResearch/hermes-agent#140958 ·
维护者通常 1 天内回复
-
Bug triage/confirmed
难度 2/5 半天 新手友好度 85/100
agentscope-ai/agentscope#3355 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 95/100
ethereum/execution-specs#3859 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复