How to implement cards migration? #11
Labels
discussion
There's a lot to discuss
documentation
Improvements or additions to documentation
enhancement
New feature or request
There is a distant idea that card migration could be implemented.
Why?
MyCard.index
. We wanted to makeMyCard.currentIndex
. In the SP this lives with theindex
key, and the new desired key iscurrentIndex
(let's say the naming matches the enumeration - it doesn't matter now). I'd like to add adeprecated
annotation to the old card and create a new card + specify "something" for migration.shared_preferences
package. Now we would like to useCardoteka
and move all the old keys to the new addresses (re-saving the values of course)I think it should be in
CardotekaConfig
as a field and passed as a parameter. Implementation can be done as a getter when definingMyCard
's (or wherever). I would like to use a separate class, but inMap
form I see it like this (pseudo code):There's an important point here: we want to transfer values to another key in SP (and delete the old key).
The text was updated successfully, but these errors were encountered: