Skip to content
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 README.md #3

Merged
merged 1 commit into from
Feb 15, 2018
Merged

Update README.md #3

merged 1 commit into from
Feb 15, 2018

Conversation

qgadrian
Copy link
Contributor

Updated the hex dep version.

As well I updated the topic send example since for sending a message to a topics it's required the following format /topics/$topic

As a suggestion, I would consider validating the correct format and five user info about this error, since the one from Google it's not clear enough (returns an error %{"error" => "InvalidRegistration"}). Or even I would consider prepending the /topics/ string to the given one if does not match the required format.

Updated the hex dep version.

As well I updated the topic send example since for sending a message to a topics it's required the following format `/topics/$topic` (see https://firebase.google.com/docs/cloud-messaging/http-server-ref)

As a suggestion, I would consider validating the correct format and five user info about this error, since the one from Google it's not clear enough (returns an error `%{"error" => "InvalidRegistration"}`). Or even I would consider prepending the `/topics/` string to the given one if does not match the required format.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 73.913% when pulling e10ed4d on qgadrian:patch-1 into a17591a on shufo:master.

@shufo
Copy link
Owner

shufo commented Feb 15, 2018

@qgadrian

Thanks for updating README!

As a suggestion, I would consider validating the correct format and five user info about this error, since the one from Google it's not clear enough (returns an error %{"error" => "InvalidRegistration"}). Or even I would consider prepending the /topics/ string to the given one if does not match the required format.

According to your suggestion, I will try to verify the topic name so that it returns a tuple like {:error, "Topic name requires format: '/topics/name'"} in the case of an error.

@shufo shufo merged commit befdc9b into shufo:master Feb 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants