Community
Participate
Working Groups
Build Identifier: M20100909-0800 In Sapphire 0.2 release, there are a few new classes which extend SapphireCondition. For classes that need to be migrated to extend SapphireModelCondition rather than SapphireCondition, if they contain parameters, they need to override SapphireModelCondition's initCondition() method. But the overridden method need to call super's initCondition() method to ensure that model dependencies and listeners are handled properly. Failure to do that would result the conditions never re-evaluated when the corresponding model properties change. We need to add some documentation in regard to this issue in the Sapphire 0.2 migration guide. Reproducible: Always
Added some wording about this to the migration guide. Please verify.
Just the release doc and found this note: It is important that any subclass of SapphireModelCondition that overrides initCondition() method, also calls the super implementation of this method. Failing to do that will prevent the condition from refreshing on dependent property changes.
Closing.
