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
{{ message }}
Repository navigation
Allow specifying custom type converters per table or globally too #899
Currently, to convert a custom type, we have to annotate each field of that type individually with @convert.
This is very inconvenientt, because if you have a custom type, e.g. joda.time.DateTime you'll always want to convert it, so it would be much cleaner and less error-prone if we could define custom type converters per table or for the whole database too, like Room does it with TypeConverters.
Describe the solution you'd like
For a per-entity definition of converters, one could extend the @entity annotation something like this:
@Entity(converters={@Convert(...), @Convert(...),...}
public class User ...
For defining converters globally, the ObjectBox builder could be extended.
Describe alternatives you've considered
Currently, the only alternative is to add @convert to each and every field.
Additional context
As said above, you can have a look at Room's @TypeConverter annotation that can be applied to METHOD, PARAMETER, TYPE and FIELD.
Activity
greenrobot-team commentedon Aug 17, 2020
Thanks! Please thumbs up if you would like to see this feature in ObjectBox.