Closed FredericRuaudel closed 4 years ago
@FredericRuaudel thank you for the pull request! ❤️
deprecated
to save backward compatibilityMaybe it'd look better, yeah 🙂 but we definitely should keep old way too just by marking it deprecated to save backward compatibility
I'm not sure we understand each other here, I've added those computed properties so I could have change the name right now and no need for deprecated
marker. Or I didn't get what you said? 🤔
Maybe it'd look better, yeah 🙂 but we definitely should keep old way too just by marking it deprecated to save backward compatibility
I'm not sure we understand each other here, I've added those computed properties so I could have change the name right now and no need for
deprecated
marker. Or I didn't get what you said? 🤔
Yeah, my bad, sorry I was in a hurry 🙂 no questions! all good! 🙂
In order to test my model properties, I need to access the properties values of the APNs data models.
As they are already public in the Android side, I imagine this is not a deal breaker to homogenize it on the Apple side?
I just have a few doubts on the final result:
private(set)
(I didn't add it since Android is fully public)FCMApnsAlertOrString
public to make Swift compiler happy inFCMApnsApsObject
(aka: can't set property public because type used in not public yadiyada)FCMApnsAlertOrString
helpers to access the enum associated values:alertPayload
/alertMessage
orasPayload
/asMessage
orasPayload
/asString
at call site it looks like this right now:
so maybe it would look better like this:
🤔
What do you think?
Thanks in advance!