this post was submitted on 08 Oct 2024
22 points (95.8% liked)

Programming

17153 readers
493 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi
22
How to ensure my web app has backward compatibility with importing JSON based user data? (lemm.ee)
submitted 15 hours ago by jonathanvmv8f@lemm.ee to c/programming@programming.dev
5 comments fedilink hide all child comments
 

I am working on a small web app that stores user data locally using indexedDB which can be imported/exported by making use of JSON files. Since I plan on adding updates to the site, I want to know what best practices I should follow to make sure my app can allow importing of user data from older versions. It could be related to how I should define the properties of my user data object to make it future proof, or any library or tool I could implement that would make this migration process easier.

Do keep these points in mind:

  1. I am using NextJS to build this application and Dexie to manage indexedDB
  2. Without going into details, the user data file makes use of heavily nested objects and arrays and most likely won't fit in a cookie or even in the local storage API
  3. This web app acts as a proof of concept which must only make use of the aforementioned core technologies, regardless of whether more efficient alternatives exist or not.
you are viewing a single comment's thread
view the rest of the comments
[–] Ephera@lemmy.ml 15 points 14 hours ago

Two rules of thumb that I've found useful:

  1. Introduce a version field top-level. If necessary, you can introduce a version 2, but keep the parser for version 1 around.
  2. You want to err on the side of using objects in place of single values, because you can add fields to an object without breaking backwards compatibility.