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

#32 - Update either-or #46

Merged
merged 1 commit into from
Aug 7, 2017
Merged

#32 - Update either-or #46

merged 1 commit into from
Aug 7, 2017

Conversation

Alfredo-Delgado
Copy link
Contributor

@Alfredo-Delgado Alfredo-Delgado commented Jul 31, 2017

  • return undefined and dev.warn in console if neither a or b match ~chosen
  • add tests including compute use
  • update documentation

Resolves #32

get: function(chosen, a, b){
return b !== chosen();
get: function(chosen, a){
return a === chosen();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it's important to change this, now. Without this change, the case where chosen() doesn't match a or b results in a checked checkbox without the chosen value being updated to a or b.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd suggest we even take it a step further and set chosen(b) if chosen() !== a.

@Alfredo-Delgado Alfredo-Delgado changed the title Update documentation for either-or and make false the default state… #32 - Update either-or Aug 1, 2017
@Alfredo-Delgado Alfredo-Delgado force-pushed the 32-either-or branch 2 times, most recently from 2b525cb to 14cc828 Compare August 2, 2017 14:49
QUnit.equal(map.pref, "Yes", "map updated because check was checked");
});

QUnit.test("supports computes", function() {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@justinbmeyer I added this test using computes. Does this answer your question?

  - return `undefined` and dev.warn in console if neither `a` or `b` match `~chosen`
  - add tests including compute use
  - update documentation
@phillipskevin phillipskevin merged commit 056cd8a into master Aug 7, 2017
@phillipskevin phillipskevin deleted the 32-either-or branch August 7, 2017 17:13
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