How to avoid translation issues in setState @deeecode
How to avoid translation issues in setState  @deeecode
Uploaded October 2025 | Updated September 2026, 1 week ago
I got feedback on a change I made this week in my company; it had to do with translations. I was saving translations in state and that created a discrepancy where the user could change the translation, but they still see the content of the previous translation.

I've learnt the fix, and I made a video about it here.

The code for the project is here: github.com/dillionmegida/demos/tree/main/react-locale
But note that this is not the most optimal way to set up translations for your project. This example was just for demo purposes

Subscribe to My Channel: bit.ly/deeecode
How to avoid translation issues in setState#3 What is a Git Repository?How Does Netlify Create Dynamic Deployment Status Badges?Why is your POSITION:STICKY not working? Two main reasons, with solutions#1 What is VERSION CONTROL? And DISTRIBUTED VERSION CONTROL?#13 Discriminating Unions | Simple TypeScript CourseStop Deleting Your Temp Changes Before Every Commit — Use This InsteadCustom Search on Browser #deeecode #shorts #chromeCSS Resources for Easy Effects #shorts #cssReactElement vs ReactNode #typescript #shortskeyof typeof magic in TypeScript #typescript #shorts#9 Build React Applications Online With CodeSandBox.io
Deeecode |

How to avoid translation issues in setState

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER