-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs and migration guide after builder api changes #3422
Conversation
Apollo Android 3.x instead uses Kotlin default arguments and exposes constructors as top-level functions. | ||
|
||
For example, for `ApolloClient`: | ||
On Apollo Android 2.x you would use the `ApolloClient.builder()` method to instantiate a new Builder. With 3.x, use the `ApolloClient.Builder()` constructor instead (notice the capital `B`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a deprecated builder()
for the transition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely! Adding this to #3410.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments but LGTM!
Co-authored-by: Martin Bonnin <[email protected]>
A followup of #3404.
Note: as discussed I've removed the Java snippets from the normalized cache doc, and that means we will probably need a specific "Java how-to" page 😊