Import 0.x stores into SQLite on first start

未关闭
  • 哪里不对？
#53 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
57/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java, sqlite
领域
backend, databases

调研方向

Start by reading the implementation and migration plan for dependency #52, then inspect how the plugin currently reads its 0.x HOCON stores file and initializes SQLite. Add coverage using a sample legacy file with malformed entries. Done means the first start imports stores, items, prices, and balances, reports skipped entries, preserves the old file under a migrated name, and a restart does not import again.

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

描述

enhancement

Problem

Servers upgrading to 1.0 have their stores in the old HOCON file. They need to keep them when storage moves to SQLite.

Scope

  • On the first start with an empty database, read the old stores file and write everything into SQLite.
  • Rename the old file afterward (for example stores.conf.migrated) instead of deleting it.
  • Log a clear summary: stores imported, and anything skipped and why.
  • Convert custom messages in config.yml to the new message format, if the messaging rework (#20) has landed by then.

Done when

  • A 0.4.0 data folder upgrades to 1.0 with every store, item, price and balance intact.
  • Restarting after the import doesn't import again.
  • Tests cover a sample 0.x file, including malformed entries.

Depends on #52.

主要语言
Java
星标
1
派生
0
平均合并
2 小时 35 分钟
30 天内合并 PR
14

环境准备

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

从这里开始

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

BrendonButler/Shops 的其他 Issue

查看 BrendonButler/Shops 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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