You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
-[ ]#97: In commit 65a6593229ae8bad1630a82ccebb327fb4a9f1e3, Daniel removes a few tests based on Core Data. Make sure that we still have tests for Core Data: attributes are safe keys, and they should be rendered.
The reason will be displayed to describe this comment to others. Learn more.
Hi, those two tests although they were touching into Core Data they were no longer needed after we removed the preventNSUndefinedKeyExceptionAttack feature correct? Is this a reminder to add extra Core Data related tests or did I do something wrong?
The reason will be displayed to describe this comment to others. Learn more.
Yes, Daniel. We need to test that Core Data attributes are visible from templates.
The safety mechanism makes {{ x }} fail unless x is "safe", which means backed by a property, or by Core Data (Core Data attributes are not exposed as ObjC properties, and require extra check).
So unless we have an explicit test for it, we may break Core Data support without noticing it.
This TODO item is just a reminder. Maybe we already have a test, maybe not.
7a1880f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, those two tests although they were touching into Core Data they were no longer needed after we removed the preventNSUndefinedKeyExceptionAttack feature correct? Is this a reminder to add extra Core Data related tests or did I do something wrong?
7a1880f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, Daniel. We need to test that Core Data attributes are visible from templates.
The safety mechanism makes
{{ x }}
fail unlessx
is "safe", which means backed by a property, or by Core Data (Core Data attributes are not exposed as ObjC properties, and require extra check).So unless we have an explicit test for it, we may break Core Data support without noticing it.
This TODO item is just a reminder. Maybe we already have a test, maybe not.