implement consistent approach to state management
See original GitHub issueThis issue was generated by todo based on a TODO
comment in 33ec75cf51bdd1b4c129573de90e87fa6455cbc3 when #866 was merged. cc @FightPandemics.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
State-based consistent messaging - Exactly Once
The implementation of state-based consistent messaging has some gaps that require mentioning. First, in most real-world applications the state version storage ...
Read more >Distributed State — Challenges and Options | The Startup
Depending on the consistency requirement, it's usually a mix of the above approaches used for distributed state management.
Read more >What is State Management? - TechTarget
Application state management is the process of maintaining knowledge of an application's inputs across multiple related data flows that form a complete ...
Read more >Demystifying state management - DEV Community
State management is one of the most complicated, and opinionated topics in modern and JavaScript-focused front-end development.
Read more >3 Effective Ways To Implement State Management In Next.js
In this article, we are going to discuss different state management methods that we can use with a Next.js web app I will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Haha lol okay I see 79229e366eb85cf34f74ce233b65c185f28707c5 did indeed resolve it but not in the way I intended. I meant overall let’s come up with an approach. I’ll be more careful of my todo messages here on out…
We need to use redux for user/profile state management (e.g. updating org name) at least until we have a new approach 33ec75cf51bdd1b4c129573de90e87fa6455cbc3 .
I’ll create a new issue - we don’t have many users creating orgs yet now hopefully soon & they will notice.
@tejasm2 I’m just going to remove the
TODO
comments and close this (tomorrow) . I will re-word and create a new issue. Maybe for these kinds of issues we should use “refactoring” or “tech debt” label