Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

chore(deps): drop shadcn_flutter: barrel re-export, imports, third_party, guard (#1465)

未關閉
#1,736 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
38/100
Issue 類型
重構
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
dart, flutter

研究方向

Start with lib/shared/widgets/widgets.dart, shared_does_not_import_shadcn_test.dart, and the shadcn_flutter entries in pubspec.yaml; the issue describes the affected imports and dependency cleanup. Check how the existing guard test is structured, then use the stated grep and flutter pub get checks as initial verification. Done means no package references remain in lib/ or the dependency configuration, tests and goldens pass, and Linux, Windows, and macOS release builds succeed.

由索引模型根據 Issue 內容生成。

描述

frontend P2 ui

Part of #1465 (step 6, the last).

Problem

After #1729–#1735 nothing in lib/ needs shadcn, but about 500 files still get Flutter itself (Text, Widget, setState, Row, BuildContext...) through export 'package:shadcn_flutter/shadcn_flutter.dart' in lib/shared/widgets/widgets.dart, and 59 files import the package directly. A probe on dev (2026-10-18) that removed the import from all of them left 174 files needing only a Flutter import.

Change
  • Add import 'package:flutter/widgets.dart'; (or material.dart) where a file used the barrel for Flutter types.
  • Remove the shadcn re-export from the barrel and every package:shadcn_flutter import.
  • Drop third_party/shadcn_flutter and its dependency_overrides / dependencies entries; flutter pub get.
  • Guard test: no package:shadcn_flutter anywhere in lib/ (extends shared_does_not_import_shadcn_test.dart).
Acceptance
  • grep -r "package:shadcn_flutter" lib is empty; the package is gone from pubspec.yaml and third_party/.
  • All tests and goldens pass; release builds for Linux, Windows and macOS build.
主要語言
Dart
星號
23
分支
1
平均合併
35 分鐘
30 天內合併 PR
497

環境準備

在 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 摘要。