Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

ui: QueryaTextField, one text input for every form (#1465)

未关闭
#1,733 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
dart, flutter
领域
frontend

调研方向

Start by reading the kit’s existing QueryaSearchField and QueryaControlSize, then locate the shadcn TextField and InputFeature usages in lib/. Add widget tests for sizes, the obscure toggle, errors, and leading/trailing slots, and run the existing form tests. Done means the fields are migrated, field and button heights align, and no shadcn TextField or InputFeature remains in lib/.

由索引模型根据 Issue 内容生成。

描述

frontend P2 ui ux

Part of #1465 (step 4b).

Problem

Text inputs are shadcn's TextField in 56 places (31 files), plus InputFeature.leading/trailing in 3; another 18 are material.TextField styled by hand. The kit has only QueryaSearchField. Most uses on dev (2026-10-18): connection forms and the SSH tunnel section (17), Redis editors (16), Mongo (8), extensions, settings.

So inputs differ in height, border, focus ring and padding between forms, and between a shadcn field and a Material one in the same dialog.

Change
  • QueryaTextField in the kit: sizes from QueryaControlSize (sm / md / lg, the heights the buttons use), placeholder, leading / trailing slots (icon or button, replacing InputFeature), obscure with a reveal toggle, multiline, error text, disabled / read-only, colours from the theme tokens.
  • Migrate the shadcn fields first, then the hand-styled Material ones; keep keys and controllers.
  • Guard: no shadcn TextField / InputFeature in lib/.
Acceptance
  • One field component; a field and a button in one row have the same height (the #1480 item about the path field and Browse…).
  • Widget tests: sizes, obscure toggle, error, leading / trailing; existing form tests pass.
主要语言
Dart
星标
23
派生
1
平均合并
31 分钟
30 天内合并 PR
570

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。