-
Notifications
You must be signed in to change notification settings - Fork 248
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
Added topic subscription information retrieval to messaging client #362
base: dev
Are you sure you want to change the base?
Conversation
* chore: Added Actions-based release workflow * Set GOPATH * Fixed working directory for tests * Decrypting credentials into the testdata directory * Added preflight and post check scripts
…firebase#335) According to the document https://developers.google.com/instance-id/reference/server, the endpoints should be: https://iid.googleapis.com/iid/v1:batchAdd https://iid.googleapis.com/iid/v1:batchRemove NOT: https://iid.googleapis.com/iid/v1/:batchAdd https://iid.googleapis.com/iid/v1/:batchRemove
Co-authored-by: Hiranya Jayathilaka <hiranya911@gmail.com>
corresponding tests. This commit should provide the feature requested in FR firebase#99.
@chong-shao is this something the FCM team is interested in releasing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this PR is changing based on an old version of the go SDK. Could you make it to be based on a recent version?
Also looks like there a several Github Actions build errors.
@chong-shao there's a product decision to be made here. Do we even want to expose this API in our SDKs? We ought to run this by a PM first. |
@hiranya911 synced with our PM. The feedback is that we should not merge this into master branch unless the endpoint has been switched to the new one (which has not been set up yet). Can we put this in a side branch? Or keeping the PR in open status until the new endpoints are ready? @andirayo |
@chong-shao I agree. We can keep the PR open for now. We also possibly need an API proposal, and at least a semblance of a plan to have the same API exposed in other languages at some point. |
This commit should provide the feature requested in FR #99.