-
Notifications
You must be signed in to change notification settings - Fork 6
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
Enum improvements #305
Comments
I moved to this pattern for DisturbanceType in this commit d538c9d, @pixelzoom would you mind doing a micro-review before I continue? Also, I noted that unfortunately WebStorm doesn't know how to highlight this too well and is showing a lot of gray underlines: |
Looks good to me. |
I fixed up the other enums, @pixelzoom can you please review? Close if all is well. |
Enumerations look great. Questions about a few related fields: (1) Should this field in Scene be documented as "read-only"? // @public {WaveSpatialType}
this.waveSpatialType = ... (2) I wonder if this Property in SoundScene might be better named // @public - indicates the selected view for sound
this.viewSelectionProperty = new Property( SoundScene.SoundViewType.WAVES, {
validValues: SoundScene.SoundViewType.VALUES
} ); (3) Similarly in DiffractionModel, I wonder if this Property might be better named // @public - selected scene
this.sceneProperty = new Property( DiffractionModel.ApertureType.CIRCLE, {
validValues: DiffractionModel.ApertureType.VALUES
} ); |
Thanks, I followed your recommendations, ready for review. |
👍 Closing. |
Let's follow the proposal in phetsims/phet-core#53 and reassign to @pixelzoom when ready.
The text was updated successfully, but these errors were encountered: