You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding that nobody uses GCM anymore, so perhaps it is time for the upgrade?
My suggestion would be to rename GCM model to FCM model (breaking change) and add platform choices/enum to it, like I've done in the #615
I agree perhaps there is no reason to keep the GCM model anymore and message_type but it will be a (small) breaking change.
What are your thoughts?
Rename GCM to FCM?
Keep GCM as a proxy model for backward compatibility? (seems like unnecessary work)
platform choices:
a) android, ios, web - full text in the database consistent with the rest of the library
b) a, i, w - save space
c) 0, 1, 2 - save space, easy indexing, sorting
d) new django enums
The text was updated successfully, but these errors were encountered:
My understanding that nobody uses GCM anymore, so perhaps it is time for the upgrade?
My suggestion would be to rename GCM model to FCM model (breaking change) and add
platform
choices/enum to it, like I've done in the #615I agree perhaps there is no reason to keep the GCM model anymore and
message_type
but it will be a (small) breaking change.What are your thoughts?
Rename GCM to FCM?
Keep GCM as a proxy model for backward compatibility? (seems like unnecessary work)
platform choices:
a) android, ios, web - full text in the database consistent with the rest of the library
b) a, i, w - save space
c) 0, 1, 2 - save space, easy indexing, sorting
d) new django enums
The text was updated successfully, but these errors were encountered: