Skip to content

Conversation

@cammace
Copy link

@cammace cammace commented Jun 22, 2017

Looking into the AutoValue suggestion in #450, I successfully converted two model classes to see how this would work. There are going to be significant API breaking changes if we want to fully implement this. I also didn't mess around with adding Builders for each class since you can call create() passing in all the params and receive a built object.

Using AutoValues also enforces classes to be immutable which makes sense for these models, you can currently call setRoute at any time after constructed.

Would love to hear your thoughts on this @zugaldia

@zugaldia
Copy link
Member

@cammace Please let me know once CI is happy and I'll give this one a pass.

@cammace
Copy link
Author

cammace commented Jul 31, 2017

I'm going to go ahead and close this PR in favor of a new one which moves logic over to AutoValue. This PR was more of an experiment to learn about the cost and benefits of using AutoValue.

@cammace cammace closed this Jul 31, 2017
@cammace cammace deleted the cam-auto-value branch August 1, 2017 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants