@ryanflorence Both. Theme colors originate in CSS custom properties, React provider can orchestrate light and dark mode, and read in the custom properties to use in JS needs them (icon props, etc)
The React Provider Pattern es un buen artículo para empezar a pensar en los patrones de aplicación de Context + Hooks una vez que has digerido la parte lógica https://t.co/vKNsQkqO4D
@balazsorban44@babeljs A nice thing about this terrible approach was that I had a front end drop down menu that could hot-load new dictionary to change language in the SPA on the fly
e.g. by calling `/api/lang?lang=en` & stuffing the result in a global, it would update the React <Provider> and so UI
"Your body can withstand almost anything; it is your mind that you have to convince." Sadly, this isn't the case with injuries! We often see athletes trying to convince themselves that they're not hurt & doing more damage to their bodies. Your local #REACT provider can help! https://t.co/KJBpBMw9w6
@dai_shi@Joseptec Yeah the “apps may become out of sync” seemed to suggest this is more akin to a global variable / shared mutable state, rather than a hoisted react provider. Thanks for confirming
Are you a leader in rehabilitation?
Become a #REACT provider today and begin treating your patients with the world's most advanced muscle stimulation system that is setting a new standard in athletic training, recovery, and physical therapy: https://t.co/z5UFBxXycb#REACTpthttps://t.co/RwyCQ6zWY7
My thoughts on using React Context and the React Provider Pattern as a design pattern and major building block in modern React applications: https://t.co/LVkfqSnu4z#react#webdev