Know how this copy was installed, and update the way that install should
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with src/Prompuff.Infrastructure/Updates/VelopackUpdateService.cs and its IsSupported and CheckForUpdatesAsync methods, then read IUpdateService, DiagnosticReport, and the Updates section in SettingsViewModel. Record the install approach in ROADMAP.md; the issue calls for tests covering each install type and documentation in docs/user-guide.md. Done means Settings and diagnostics reflect each install type’s update behavior, and the guide explains it.
由索引模型根据 Issue 内容生成。
描述
A copy that came from a package manager shouldn't update itself. Today nothing in the code tells a portable, installed, AppImage or packaged copy apart: DiagnosticReport prints only "installed" or "development build".
What to do
- Prompuff knows how it was installed: the Windows installer, the portable zip, an AppImage, a
.deb, the AUR or a Flatpak. A package can carry a read-only marker beside the app, and a Flatpak setsFLATPAK_ID. Record the approach in ROADMAP.md. - A
.debor AUR copy checks for updates as before, but points to the new download or the package manager instead of installing it. A Flatpak leaves updates to Flathub and doesn't check. - Settings › Updates says how this copy updates, and Copy diagnostic info names the install type.
- The Velopack check stays the only network code, and it stays switchable in Settings.
Where to look
src/Prompuff.Infrastructure/Updates/VelopackUpdateService.cs:IsSupported,CheckForUpdatesAsyncsrc/Prompuff.Application/Interfaces/IUpdateService.cssrc/Prompuff.Infrastructure/Diagnostics/DiagnosticReport.cssrc/Prompuff.App/ViewModels/SettingsViewModel.cs: the Updates section
Done when
- Each install type shows the right update behavior in Settings › Updates, and tests cover each one.
-
docs/user-guide.mdsays how each kind of copy updates.
- 主要语言
- C#
- 星标
- 0
- 派生
- 1
- 平均合并
- 1 小时 21 分钟
- 30 天内合并 PR
- 22
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
hazeliscoding/prompuff 的其他 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
hazeliscoding/prompuff#34 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
hazeliscoding/prompuff#22 ·
维护者通常 1 天内回复
-
good first issue
难度 2/5 1-3 小时 新手友好度 90/100
hazeliscoding/prompuff#14 ·
维护者通常 1 天内回复
-
good first issue
难度 1/5 1-3 小时 新手友好度 92/100
hazeliscoding/prompuff#13 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
hazeliscoding/prompuff#12 ·
维护者通常 1 天内回复
查看 hazeliscoding/prompuff 的全部 Issue
相似的 Issue
-
area-multitenancy area-security p1-recommended priority-high technical-debt
难度 2/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
-
help wanted needs-unity ready for a contributor
难度 2/5 1-3 小时 新手友好度 78/100
eyalgolan/statecraft-israel#1542 ·
维护者通常 1 天内回复
-
kind/enhancement Provider Upgrade pulumi/pulumi-azure R1 Task
难度 2/5 1-3 小时 新手友好度 65/100
pulumi/pulumi-azure#3669 ·
-
[BUG] FromCString causes 1 byte OOB read in native code可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭type/bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复