Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

1.0: freeze the .fwincident schema and commit to forward migration

オープン
  • 何か問題がありますか？
#351 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp, sqlite
領域
databases, documentation, testing

調査の方向性

Start with src/LageBuch.Persistence/Sqlite/Migrations.cs, README.md, and the existing docs to understand the current schema and migration behavior. Review the historical schema versions, PDF export, and existing migration coverage before deciding what fixtures and tests are needed. Done means the German 1.x compatibility and forward-compatibility rules are documented, old-file fixtures are tested, the schema review is recorded, and export is confirmed as an escape hatch.

索引モデルが issue の本文から書いたものです。

説明

enhancement help wanted

Every incident lives in one .fwincident SQLite file. The README tells users
plainly that the format can still change between versions before 1.0. That
warning is the single biggest reason a Wehr would hesitate to run Lagebuch on a
real Einsatz rather than an Übung.

Version 1.0 means retiring that warning. This issue tracks what has to be true
first.

The mechanism that already exists
  • src/LageBuch.Persistence/Sqlite/Migrations.cs carries CurrentVersion and
    migrates older files forward on open.
  • UnsupportedSchemaVersionException rejects a file written by a newer version
    with a clear message instead of corrupting it.

So the machinery is in place. What is missing is the commitment.

What 1.0 requires
  • A written compatibility guarantee. A file written by 1.x opens in every
    later 1.x. State it in README.md and in docs/, in German, because the
    audience for the promise is the Kommandant, not the developer.
  • Migration tests as a standing gate. A fixture file per historical schema
    version, checked into the repo, with a test that opens each one and asserts
    the migrated result. Today's coverage tests the migration code; this tests the
    actual old files.
  • A schema review before the freeze. One deliberate pass asking what we
    would regret. After 1.0 a mistake costs a migration forever.
  • A documented forward-compatibility story. What a 1.0 build does with a file
    from 1.4. Today it refuses with a message, which is defensible, but it should
    be a stated rule rather than an implementation detail.
  • Export as the escape hatch. PDF export already exists. Confirm it is
    complete enough that a user is never trapped in the format.
Not in scope

Feature work. 1.0 is a promise about the file, not a feature set.

Discussion welcome. This is the milestone that turns Lagebuch from something a
Wehr tries into something a Wehr relies on.

New here?

Comment to claim this issue and it is yours. If no pull request appears within
seven days it goes back in the pool, no hard feelings.

Before you open the PR, please skim CONTRIBUTING.md:
commits need DCO sign-off (git commit -s) and a Conventional Commit subject.
Changes under src/ additionally need an entry under ## [Unreleased] in
CHANGELOG.md — CI fails the PR otherwise.

Questions are welcome right here or in
Discussions.

主要言語
C#
スター
1
フォーク
3
平均マージ
4時間 49分
マージ済み PR（30日）
177

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CodeForFire/lagebuch のほかの issue

CodeForFire/lagebuch の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。