Storing localization strings client-side instead of sending with each request? #490
Unanswered
jameswhayman
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey guys,
I'm building a multi-lingual language learning app, and I'm starting to realise that I'll need a better way of handling the Laravel JSON localization string objects that I'm currently sending as part of each request using the Inertia::share adapter.
As these strings will only change when I roll out an app update, they can effectively be cached until a new app version is released.
The Inertia documentation covers local state saving/management for forms, but I haven't found any references to saving shared data locally.
Is there any way to do this using Inertia, or do I need to roll my own solution for this?
If anyone has any pointers/guidance or has done this before and can link me to some examples, I'd be very appreciative.
Beta Was this translation helpful? Give feedback.
All reactions