[CHORE]: Script to render every screen in every theme to PNG

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Read mobile/test/ui_smoke_test.dart for the provider setup and sample data, then inspect mobile/assets/fonts/Inter/ and the Flutter test APIs for capturing images. Build a test-based script covering the listed screens, themes, and sizes, with PNG output outside the repository; document how to run it in CONTRIBUTING.md. Done when the requested screens can be rendered with the bundled fonts and the instructions work for UI pull requests.

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

描述

area: mobile chore difficulty: medium testing

Context

While redesigning the app (#224) it was very useful to render every screen, in every theme, to PNG files with sample data and the real Inter font, and look at them side by side. That made layout problems obvious without a phone (one of them became #240). The script that did this wasn't committed.

What to do

  • Add a test-based script (e.g. mobile/tool/screenshots_test.dart, not run by default flutter test) that renders the main screens (sign-in, register, chat list, chat, group chat, contact and group info, new chat, settings pages) with sample data.
  • Load the bundled Inter font and Material Icons, so text renders properly instead of the test font.
  • Choose themes and sizes by environment variables, e.g. THEMES=frost,nebula, and write the PNGs to a folder outside the repo.
  • Document how to run it in CONTRIBUTING.md, for UI pull requests.

Where to look

mobile/test/ui_smoke_test.dart already sets up the providers and sample data; mobile/assets/fonts/Inter/.

Good to know

Capture with a RepaintBoundary around the app and toImage() inside tester.runAsync. Screens with entrance animations need a few seconds of pump first.

主要语言
Dart
星标
9
派生
5
平均合并
49 分钟
30 天内合并 PR
34

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

CommandLineCoding/Elephant 的其他 Issue

查看 CommandLineCoding/Elephant 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

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