Skip to content

Gut internal intermediate state from checkbox #751

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

Conversation

interactivellama
Copy link
Contributor

Simplify checkbox logic. Assumption is that if you need a checkbox to be indeterminate, then it is a controlled component and does not need internal state.

@chriscorwin Tell me if there's an edge case I'm missing here.

chriscorwin and others added 17 commits October 11, 2016 11:01
…es the rendered DOM structure to match SLDS, previously we were spitting out non-compliant markup that wouldn't work for indeterminate.
…tatable again. Updates indeterminate story to deal with new backwards-compatible data returned by onChange (checked [boolean], event, data [object {checked, indeterminate}]).
… into GH-626---checkbox-needs-an-indeterminate-state-21
@tweettypography tweettypography temporarily deployed to design-system-react-com-pr-751 October 31, 2016 21:31 Inactive
@interactivellama interactivellama force-pushed the GH-626---checkbox-needs-an-indeterminate-state-21 branch from e92e0f7 to da4393c Compare October 31, 2016 21:35
@chriscorwin chriscorwin merged commit edd8660 into salesforce:master Nov 1, 2016
@interactivellama interactivellama deleted the GH-626---checkbox-needs-an-indeterminate-state-21 branch December 14, 2016 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants