shahondin1624/ShadowrunCharSheet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

No version migration system for schema changes #104

New Issue
Closed
opened 2026-04-04 18:42:22 +02:00 by shahondin1624 · 0 comments
shahondin1624 commented 2026-04-04 18:42:22 +02:00
Owner
Copy Link
Copy Source

Description

All @Serializable model classes have version: String = "v0.1" but no migration logic exists. When the schema changes (new fields, renamed fields, structural changes), old saved characters will fail to deserialize with no recovery path.

Files

  • All model classes implementing Versionable

Expected Behavior

  • Version migration functions that transform old schemas to current
  • Graceful handling of unknown fields or missing fields
  • Clear version bump strategy

Acceptance Criteria

  • Migration system that handles v0.1 → v0.2 (and future) transitions
  • Unknown fields in JSON are ignored (not crash)
  • Missing fields use sensible defaults
  • Version is checked on load and migration applied if needed
  • Unit tests for migration paths
## Description All `@Serializable` model classes have `version: String = "v0.1"` but no migration logic exists. When the schema changes (new fields, renamed fields, structural changes), old saved characters will fail to deserialize with no recovery path. ## Files - All model classes implementing `Versionable` ## Expected Behavior - Version migration functions that transform old schemas to current - Graceful handling of unknown fields or missing fields - Clear version bump strategy ## Acceptance Criteria - [ ] Migration system that handles v0.1 → v0.2 (and future) transitions - [ ] Unknown fields in JSON are ignored (not crash) - [ ] Missing fields use sensible defaults - [ ] Version is checked on load and migration applied if needed - [ ] Unit tests for migration paths
shahondin1624 added the type:architecturepriority:must-have labels 2026-04-04 18:42:22 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
epic:cards-rework
Epic: Attribute & Talent cards rework
 epic:character-creation
Epic: Character creation & build points
 epic:character-display
Epic: Character info display
 epic:character-management
Epic: Character management (editing, persistence)
 epic:combat
Epic: Combat & Initiative
 epic:cyberware
Epic: Cyberware/Bioware system
 epic:dice-rolling
Epic: Dice rolling UX
 epic:gear
Epic: Gear, Equipment & Vehicles
 epic:magic
Epic: Spells & Adept Powers
 epic:navigation
Epic: Navigation & page structure
 epic:responsive-layout
Epic: Responsive layout foundation
 epic:testing
Epic: Automated UI testing
 priority:must-have
Priority: Must-have for MVP
 priority:nice-to-have
Priority: Nice-to-have, polish and extras
 priority:should-have
Priority: Should-have, important but not blocking
 type:architecture
Architecture/infrastructure concern
 type:bug
Bug or code defect
 type:feature
New feature request
 type:usability
UX/usability improvement
No Label priority:must-have type:architecture
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shahondin1624/ShadowrunCharSheet#104
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?