-
Notifications
You must be signed in to change notification settings - Fork 677
Remove data modifier from payments-core. #11127
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
base: master
Are you sure you want to change the base?
Conversation
Diffuse output:
APK
DEX
|
10d9fa4
to
76422fc
Compare
@@ -697,7 +697,7 @@ internal class StripeKtxTest { | |||
} | |||
} | |||
|
|||
private inline fun <reified ApiObject : StripeModel> | |||
private inline fun <reified ApiObject : Any> |
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.
Why do we marked some as Parcelable
and some as Any
?
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.
StripeModel is just a marker interface.
Thinking through this more, I think the correct answer is to remove equals/hashcode from StripeModel. Those methods are always available anyways.
2ff9940
to
7fc8207
Compare
7fc8207
to
dacef3a
Compare
Summary
This removes the data modifier from all classes in
payments-core
.Motivation
data classes are hard to maintain binary compatibility with moving forward. If merchants needed access to any of these copy methods, we will add them back as needed (or introduce a toBuilder/newBuilder pattern).