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

No jsx bind #265

Merged
merged 9 commits into from
Feb 15, 2016
Merged

No jsx bind #265

merged 9 commits into from
Feb 15, 2016

Conversation

nikgraf
Copy link
Owner

@nikgraf nikgraf commented Feb 15, 2016

No description provided.

>
{ renderedDay }
</span>
</DisabledDay>
);
}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nikgraf I do not like the idea of extracting a component which just handles event callbacks to get rid of bindings. A component should be a more logical entity and should be able to handle its styling logic and stuff like making dayKey out of date.

If we can do this kind of component it will help us in not just getting rid of bindings but also simplify these complex components.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm open to a PR to simplify the whole structure 😄

I'm not a big fan of having these components just for event handling, but it's the best option I'm aware of to avoid performance issue and therefor more important than not doing it at all.

nikgraf added a commit that referenced this pull request Feb 15, 2016
@nikgraf nikgraf merged commit bd2c8f8 into master Feb 15, 2016
@nikgraf nikgraf deleted the no-jsx-bind branch February 15, 2016 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants