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
If you're translating an array, you might want some control over the destination type -- you might, for instance, have parallel hierarchies in a server and client, and store values from various subclasses in an array, and need to translate items from one server-side subclass to a corresponding client-side subclass.
The text was updated successfully, but these errors were encountered:
At the moment, there's very little control over the translation of arrays -- Arrays don't even currently have a special annotation -- they simply use @Property, which makes it much harder to add an annotation for factory translation of items, because that wouldn't make sense for a non-array property. I think, basically, that this belongs alongside #77, along with, say, orphan removal and matchers, both of which might make sense in an array.
If you're translating an array, you might want some control over the destination type -- you might, for instance, have parallel hierarchies in a server and client, and store values from various subclasses in an array, and need to translate items from one server-side subclass to a corresponding client-side subclass.
The text was updated successfully, but these errors were encountered: