In the other modes, it works correctly, and triggers the properties to be re-parsed and trigger any configured TypeConverter.
However, in the optimization mode, this is not happening. Not sure how it is implemented, but this attribute needs to be respected or propagated to any nested property.
This is important so the UI is consistent for the user in all modes.
Comment