Skip to content
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

React in library name? #11

Closed
viskin opened this issue Jul 12, 2016 · 3 comments
Closed

React in library name? #11

viskin opened this issue Jul 12, 2016 · 3 comments
Assignees

Comments

@viskin
Copy link

viskin commented Jul 12, 2016

It seems that the library is completely free from being dependent on react. It can be used with say angular2+redux.
Any reason why it was named so?

@tshaddix
Copy link
Owner

Yep! When it was first created, the library implemented component-connecting functions similar to react-redux. It only took a day or two to realize that using a ProxyStore would allow users to take advantage of react bindings using existing react libraries, so I switched to that approach.

The name is a remnant of the original solution, and nothing more. You could easily use this with any front-end component library, as it's only focus is making chrome extensions "redux enabled".

What do you suggest? Renaming?

@viskin
Copy link
Author

viskin commented Jul 14, 2016

Oh, OK.
I don't think renaming is a good thing to do. But I'm not sure. People already know your library by its name...
I think that sure thing to do is stating in README that it can work with react, angular or any other library. So folks that use angular2 will not be frightened to try it.

@tshaddix
Copy link
Owner

Great idea! I'll mark this as a suggestion.

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

2 participants