DynamicObjects can now access fields by public name. #1571
Conversation
|
Then it won't provide access to a public name because there won't be any. Right now this behavior is a by-product of building the dynamic realm out of a typed realm config. It has a schema definition, and thus has public names available. I don't think this should be an issue as it only affects an internal function, and even if it was public we would allow users to access data using a public name if required. |
|
I don't think it is the right way to go. This indeed looks like a public change and we have tried not to leverage the typed schema information even if we could. But maybe it is as broader discussion on what the full dynamic API should support. Lets discuss in todays meeting. |
| assertFailsWithMessage<IllegalArgumentException>("Schema for type 'AlternativePersistedNameSample' doesn't contain a property named 'publicNameStringField'") { | ||
| dynamicSample.getValue("publicNameStringField") | ||
| } | ||
| assertEquals("Realm", dynamicSample.getValue("publicNameStringField")) |
There was a problem hiding this comment.
It would probably be appropriate with a comment here explaining that this is only due to the nature of asDynamicRealm that the public name is available here.
Fixes CI