Skip to content

Standardize state management with React #349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
diegonvs opened this issue Dec 18, 2020 · 1 comment
Closed

Standardize state management with React #349

diegonvs opened this issue Dec 18, 2020 · 1 comment

Comments

@diegonvs
Copy link
Contributor

When writing up some React applications, here at Recife we noticed that we needed to use Redux instead of simpler Context API to manage some states.
Context API has some limitations depending project's scope. e.g When trying to traverse more than three levels in components.
Would be a good idea to use redux only if you need and create some use cases when you need or when you shouldn't need? We could use useReducer hook with Context API that empowers developers but I don't know if this utilization covers all use cases.

/cc @oliveiraaraujo @phcp @brunobasto @matuzalemsteles

@wincent
Copy link
Contributor

wincent commented Dec 18, 2020

GitHub seems to have dropped the transfer job on the floor 😢

Most of the comments are visible over on the original (liferay/liferay-frontend-guidelines#44) but not here.

This issue is being transferred. Timeline may not be complete until it finishes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants