Properties should use type-specific subclasses where appropriate (e.g. BooleanProperty, NumberProperty, StringProperty) or provide documentation as to why they are not.

[samreid]

For #5, I saw several places that could use EnumerationProperty, and some that could use Vector2Property.

[jonathanolson]

I just fixed up what I was able to find. I definitely didn't see any place where EnumerationProperty could be used that isn't, could you clarify?

Additionally, should we open up a common code issue about Vector3Property, Bounds3Property, and other things not existing that I would have expected would have been kept in-line with the other dimensional equivalents?

[samreid]

Could EnumerationProperty be used in cases like these:

this.interiorMaterialProperty = new Property( BOTTLE_INITIAL_INTERIOR_MATERIAL );

new Property( Material.WOOD )

new Property( Gravity.EARTH, {

etc?

[samreid]

Additionally, should we open up a common code issue about Vector3Property, Bounds3Property, and other things not existing that I would have expected would have been kept in-line with the other dimensional equivalents?

Perhaps phetsims/axon#221 was intended for that? I'm OK with any of these plans:

• create an issue for making those
• create those
• just use the ones that exist and not worry about the others at the moment.

What do you recommend?

[jonathanolson]

Could EnumerationProperty be used in cases like these

Not that I'm aware of, custom gravities and materials are created dynamically and seem unsuitable to Enumeration. If there's a way to provide better phet-io support, let me know.

Perhaps phetsims/axon#221 was intended for that? I'm OK with any of these plans:

create an issue for making those
create those
just use the ones that exist and not worry about the others at the moment.

What do you recommend?

I'd defer to your judgment, I'm fine to not make changes.

[samreid]

Thanks, I forgot about the custom ones. All seems well, closing.