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
Currently there's both data and pushRegistrationId on a push event. I see no real use case for the id. Is this a leftover from when the api supported multiple registrations / channels? Let's remove it.
If the author really wants to have the id it can be read from getRegistration and we can always add it back if we find a strong use case.
The text was updated successfully, but these errors were encountered:
mvano
added a commit
to mvano/push-api
that referenced
this issue
Sep 2, 2014
Currently there's both
data
andpushRegistrationId
on a push event. I see no real use case for the id. Is this a leftover from when the api supported multiple registrations / channels? Let's remove it.If the author really wants to have the id it can be read from
getRegistration
and we can always add it back if we find a strong use case.The text was updated successfully, but these errors were encountered: