Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Feature Request] As a developer I want to be able to change metadata keys without the users losing their data #215

Closed
schroda opened this issue Jan 1, 2023 · 0 comments · Fixed by #218
Labels
enhancement New feature or request

Comments

@schroda
Copy link
Collaborator

schroda commented Jan 1, 2023

What feature should be added to Tachidesk?

As a developer I want to be able to change metadata keys (the keys saved in the "meta" property of e.g. the manga) without having users lose their data.

Why/Project's Benefit/Existing Problem

It should be possible to improve metadata key names (e.g. they have a typo or a different name would be more suiteable) without having users lose their data that has been saved under the old metadata keys.

@schroda schroda added the enhancement New feature or request label Jan 1, 2023
@schroda schroda changed the title [Feature Request] As a developer I want to be able to change metadata keys without the user losing their data [Feature Request] As a developer I want to be able to change metadata keys without the users losing their data Jan 1, 2023
AriaMoradi pushed a commit that referenced this issue Jan 6, 2023
* [#215] Handle metadata migration

Makes it possible to change "metadata keys" and the "app metadata key prefix" without losing data

* [#215] Fix checking and handling missing reader settings in metadata

With the new migration logic missing reader settings couldn't be detected anymore in case the metadata included outdated app metadata keys for the reader settings.

* [#215] Fix name of "IReaderSettings" property
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant