-
Notifications
You must be signed in to change notification settings - Fork 8
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
Deprecate PropertySet #102
Comments
@jonathanolson proposed keeping ES5 get/set in #71 (comment) and I responded in #71 (comment) |
We have to decide in #71 before doing anything here. |
…pertySet -> Property for ElectricPotentialSensor
… set() and get() for ModelElement
…pertySet -> Property for MeasuringTape; use set() and get() for properties
… types in addInstance calls
Over in #71, we decided to move away from PropertySet. So it's constructor should be annotated as |
PropertySet constructor and its public public functions as now annotated as Labeling for developer meeting to decide how to proceed with refactoring away from PropertySet. |
The repositories below use PropertySet. Shall we make an issue for each repository? common code:
simulations:
|
There are 160 occurrences of |
I removed PropertySet from simula-rasa, blast, chains and vegas. |
@ariel-phet recommended to create 30+ issues, one per each repo. Even better: Let's add a note to the "how to instrument" doc to this effect. @pixelzoom says we should fix the common code that uses propertyset. @pixelzoom will create issues for that. @jbphet will tackle ButtonModel. |
I finished removing usages of PropertySet then I deleted PropertySet. I'm going to let Bayes use UPDATE: #142 seems a better reference for emitter/events. |
Agreed, #142 is the reference for converting Events to Emitter. Looks like our work here is done? |
Good work everyone, that was a biggy! |
As discussed in #71 and #101, PropertySet creates more problems than it solves and should be deprecated. The recommended pattern is described here #71 (comment)
with reset and disposal as described here:
#71 (comment)
If anyone wants to argue that PropertySet should be kept/fixed/etc, that should happen here. Otherwise, this issue is about how and when we will move away from PropertySet. Some possibilities:
(a) Replace all PropertySet occurrences now up front, then delete PropertySet immediately.
(b) Leave existing PropertySet occurrences for now, but no new code will use PropertySet
(c) When PhET-iO instrumenting a simulation, refactor away from PropertySet
We also have the possibility to refactor PropertySet as @pixelzoom described in https://github.com/phetsims/phet-io/issues/640 as an intermediate solution.
@jessegreenberg @pixelzoom @aadish @andrewadare @jbphet @jonathanolson please comment below and we'll decide at an upcoming developer meeting.
The text was updated successfully, but these errors were encountered: