Say you have two Realm objects, Contact and Email as in this example. The support for nested member #4, makes queries like
realm.where(Contact.class).equalTo("email.active", false).findAll()
safe and nice as you can replace "email.active" with ContactFields.EMAIL.ACTIVE. However, for queries like
realm.where(Contact.class).isNull("email").findAll()
you still need to write down the string explicity since no field "email" is generated. It would be great if the string and the corresponding class object were generated, e.g. in this example ContactFields.EMAIL and ContactFields.EMAIL_FIELD or ContactFields.EMAIL_CLASS and ContactFields.EMAIL or similar.
Say you have two Realm objects, Contact and Email as in this example. The support for nested member #4, makes queries like
realm.where(Contact.class).equalTo("email.active", false).findAll()
safe and nice as you can replace"email.active"
withContactFields.EMAIL.ACTIVE
. However, for queries likerealm.where(Contact.class).isNull("email").findAll()
you still need to write down the string explicity since no field "email" is generated. It would be great if the string and the corresponding class object were generated, e.g. in this example ContactFields.EMAIL and ContactFields.EMAIL_FIELD or ContactFields.EMAIL_CLASS and ContactFields.EMAIL or similar.