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

move away from mixins #100

Closed
Haroenv opened this issue Jun 7, 2016 · 2 comments
Closed

move away from mixins #100

Haroenv opened this issue Jun 7, 2016 · 2 comments

Comments

@Haroenv
Copy link
Contributor

Haroenv commented Jun 7, 2016

As listed in react/docs/reusable-components#no-mixins ES6 react doesn't support mixins anymore. I think it would be interesting to list in the documentation here how to handle this situation.

@jwngr
Copy link

jwngr commented Jun 7, 2016

Duplicate of #38. Please join the discussion there.

For the record, mixins are still valid in ES6. They just aren't usable with the new component definition syntax. ES6 is backwards compatible and ReactFire will continue to work.

@jwngr jwngr closed this as completed Jun 7, 2016
@Haroenv
Copy link
Contributor Author

Haroenv commented Jun 7, 2016

Sorry, didn't see that issue. Thanks anyway 😄

@FirebaseExtended FirebaseExtended locked and limited conversation to collaborators Dec 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants