-
Notifications
You must be signed in to change notification settings - Fork 1
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
meanProperty should be a DerivedProperty #75
Comments
We also used the new feature |
@marlitas and I collaborated on this, and it seems ready for review. Thanks for the great recommendation! |
Looks good. A couple of nits...
|
Maybe the comment is trying to explain why const dependencies = [
...this.waterCup3DArray.map( waterCup => waterCup.waterLevelProperty ),
...this.waterCup3DArray.map( waterCup => waterCup.isActiveProperty )
];
// map() does not preserve a property of .length required for DerivedProperty
this.meanProperty = DerivedProperty.deriveAny( dependencies, |
Documentation updated in above commit. Hopefully this clarifies the comment before meanProperty. I do not fully understand the typing restrictions on derivedProperty, I just know they exist, so if further clarification is needed I'll reach out for assistance. Assigning back to @pixelzoom for review. |
👍🏼 closing. |
For code review #41 ...
For this checklist item:
This is unfortunate in IntroModel.ts, especially since it's arguable the most-important Property in the screen:
And this unfortunate compromise is due to #60. So to reiterate what I said in that issue, I would reconsider the decision to dynamically allocate pipes and cups. Or investigate other ways of allowing
meanProperty
to be a DerivedProperty.The text was updated successfully, but these errors were encountered: