Programming

17398 readers

103 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

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@lemmy.nz

How to ensure my web app has backward compatibility with importing JSON based user data? (lemm.ee)

submitted 1 month ago by jonathanvmv8f@lemm.ee to c/programming@programming.dev

16 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:

I am using NextJS to build this application and Dexie to manage indexedDB
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
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

[–] hosaka@programming.dev 6 points 1 month ago (12 children)

Use Open API schema. You can define data models and endpoints or just the models, I do this at work. Then generate your code using openapi-generator.

[–] undefined@links.hackliberty.org 1 points 1 month ago* (last edited 1 month ago) (11 children)

Do you happen to do this in Ruby on Rails? I don’t know what happened but it seems like Swagger, JSON:API, and the serializers/deserializes are all abandoned.

For personal projects I use GraphQL for everything, I’m not a fan of REST these days. Let me define a schema and let clients screw around with the data. I just won’t waste the time anymore despite the performance impact everyone might cry about.

[–] expr@programming.dev 2 points 1 month ago (9 children)

Obligatory "JSON APIs are not REST because JSON is not hypermedia".

GraphQL is a mess too as you throw out any ability to reason about query performance and it still requires thick clients with complicated/duplicated business logic.

If you're doing RoR anyway, then go for https://htmx.org/. It's much, much simpler and closer to how the web was originally designed. Highly recommend this book the author wrote on the subject (also provides tutorials walking through building an app): https://hypermedia.systems/book/contents/.

[–] hosaka@programming.dev 2 points 1 month ago (1 children)

HTMX is great by I don't think it's what OP needs since the input and desired output is not hypermedia in the first place.

[–] expr@programming.dev 2 points 1 month ago (1 children)

I was replying to someone talking about GraphQL and Ruby on rails, not the OP of this post.

[–] undefined@links.hackliberty.org 1 points 1 month ago

No but you are misunderstanding me — I’m talking about a web API for others to consume, not using GraphQL in the frontend of a website.

load more comments (7 replies)

load more comments (8 replies)