Skip to content

Accept prefixed topic names #203

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

Merged
merged 2 commits into from
Feb 8, 2018
Merged

Accept prefixed topic names #203

merged 2 commits into from
Feb 8, 2018

Conversation

hiranya911
Copy link
Contributor

The new FCM API does not accept topic names prefixed with /topics/. But we can easily check for this in the SDK and remove it. This results in a better and consistent dev experience since the other methods in this API accepts prefixed topic names.

@hiranya911 hiranya911 merged commit e9ea3ab into hkj-fcm-api Feb 8, 2018
@hiranya911 hiranya911 deleted the hkj-fcm-topics branch February 8, 2018 00:15
hiranya911 added a commit that referenced this pull request Feb 13, 2018
* New FCM API

* Adding FCM unit tests

* Added other FCM message types and tests

* Minor cleanup

* APNS message validation

* Cleaned up tests

* Improved error handling

* Updated typings and integration tests

* Updated typings

* Added APNS types in the impl

* Updated unit tests

* Implemented dry run mode

* Updated API; Implemented TTL numeric values; More test coverage

* Boosted test coverage to almost 100%

* Updated changelog

* Changing test data

* Adding some documentation; Addressing some code review feedback

* Accept prefixed topic names (#203)

* Accept prefixed topic names

* Further validating topic names

* Handling the New FCM Error Codes (#206)

* Using new FCM error codes

* Adding new SDK error code message-rate-exceeded

* Updated changelog
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