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 }}
This repository has been archived by the owner on Jun 18, 2020. It is now read-only.
When we move the data module generation to AutoValue #137, we can add a companion class generator, that will allow to build a user fields array. This is useful for resources like UserProfilesResource where the spec accepts model fields that have to be returned by the api.
This will reduce the probability runtime bugs, when using accessing a resource.
Things to keep in mind:
The api accepts nested field names as well, like field1.sub_field1.sub_sub_field2 the annotation processor will have to lookup for dependent builders.
The generated builder like class Fields should be something like:
@GenerateFields// Name not final.abstractclassXingUser {
abstractclassFields {
Fieldsfield1();
String[] build();
}
}
The text was updated successfully, but these errors were encountered:
When we move the data module generation to AutoValue #137, we can add a companion class generator, that will allow to build a user fields array. This is useful for resources like UserProfilesResource where the spec accepts model fields that have to be returned by the api.
This will reduce the probability runtime bugs, when using accessing a resource.
Things to keep in mind:
field1.sub_field1.sub_sub_field2
the annotation processor will have to lookup for dependent builders.Fields
should be something like:The text was updated successfully, but these errors were encountered: