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

Record 1.2's settings in `settings-1.2.0.json`

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
csharp, json
领域
database, testing

调研方向

Start with JsonSettingsStoreTests.cs and its Settings_saved_by_1_0_keep_every_choice test and Write_fixture helper; check how PinnedFixtures.cs and PinnedFixtureTests.cs pin fixture files. After the other v1.2 issues land, run the fixture writer and record every setting changed from default as saved on Windows. Done means the 1.2 fixture is pinned and its comparison test passes alongside the 1.0 test.

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

描述

Whatever ships joins the 1.0 promise, and settings carry over. settings-1.0.0.json holds 1.0 to that. 1.2's new settings need a recording of their own, so later versions keep them too.

What to do

  • Once the other v1.2 issues have landed, write tests/Prompuff.Infrastructure.Tests/Fixtures/settings-1.2.0.json with every setting changed from its default, as 1.2 saves it on Windows, and pin it in tests/pinned-fixtures.sha256.
  • Add a test like Settings_saved_by_1_0_keep_every_choice that compares every value in the new recording.
  • Write_fixture writes settings-1.0.0.json today. Let it write the 1.2 file instead of adding a second writer. It must keep refusing to overwrite a pinned file.
  • Never edit, regenerate or delete settings-1.0.0.json. If 1.2 can't read it, fix the code.

Where to look

  • tests/Prompuff.Infrastructure.Tests/JsonSettingsStoreTests.cs: Settings_saved_by_1_0_keep_every_choice, Write_fixture (PROMPUFF_WRITE_SETTINGS_FIXTURE)
  • tests/Shared/PinnedFixtures.cs and tests/Prompuff.Infrastructure.Tests/PinnedFixtureTests.cs

Done when

  • settings-1.2.0.json is pinned, and its test passes beside the 1.0 one.
主要语言
C#
星标
0
派生
1
平均合并
1 小时 21 分钟
30 天内合并 PR
22

环境准备

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

从这里开始

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

hazeliscoding/prompuff 的其他 Issue

查看 hazeliscoding/prompuff 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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