-
Notifications
You must be signed in to change notification settings - Fork 585
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
[Comment] Reusability aka Redux Dependency #260
Comments
I agree. Redux should not be coupled with this component. |
@ohager @Codii @thebigredgeek Thanks for your feedback!
|
You're welcome. Awesome Work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This not a bug, nor a feature request...just a comment. Discussions are welcome.
I decided not to use this component due to fact, that it uses redux as dependency.
Don't get me wrong, Redux/Flux is an adequate architectural solution for managing application state.
IMHO a reusable component should isolate its behavior and should be agnostic to any architecture pattern. Using Flux to manage a components state is not a good design decision, as it
I cannot see any good reason why react-autosuggest uses redux.
Coincidentally, I wrote a post about it some months ago, because I tried to apply Flux to a custom suggestion input.
The text was updated successfully, but these errors were encountered: