Skip to content
This repository has been archived by the owner on Jun 18, 2020. It is now read-only.

Consider AutoValue for api client models. #137

Open
serj-lotutovici opened this issue Jul 4, 2016 · 4 comments
Open

Consider AutoValue for api client models. #137

serj-lotutovici opened this issue Jul 4, 2016 · 4 comments
Labels
enhancement
Milestone
2.1.0

Comments

@serj-lotutovici
Copy link
Contributor

Currently we are declaring all models manually. This creates an overhead for us when maintaining hashCode, equals() e.t.c. AutoValue will solve this problem for us.
Another pro is the new extension api of AutoValue which gives us a rich combination of possibilities.
@dhartwich1991
Copy link
Contributor

Oh yes please!

@serj-lotutovici
Copy link
Contributor Author

@dhartwich1991 which milestone should it be? 2.0.0 or 2.1.0

@dhartwich1991
Copy link
Contributor

My opinion would be to get 2.0.0 out and then make it part of 2.1.0, agree?

@serj-lotutovici
Copy link
Contributor Author

My opinion would be to get 2.0.0 out and then make it part of 2.1.0, agree?

Yes

@serj-lotutovici serj-lotutovici added this to the 2.1.0 milestone Jul 4, 2016
@serj-lotutovici serj-lotutovici mentioned this issue Aug 3, 2016
Open
@aballano aballano mentioned this issue Oct 16, 2016
Merged
1 task
@serj-lotutovici serj-lotutovici mentioned this issue Oct 19, 2016
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@serj-lotutovici @dhartwich1991