-
Notifications
You must be signed in to change notification settings - Fork 24
Add custom message type support #191
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
Conversation
e8987ac to
cb4c9b4
Compare
parfeon
left a comment
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.
LGTM!
| ) | ||
| case file( | ||
| message: FilePublishPayload, | ||
| customMessageType: String?, |
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.
@jguz-pubnub I'm wondering about this one. Don't see it in specs so far. I know that it should be the same as regular publis.
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.
Indeed, there's no mention about it in specs. I asked Smitha and here's the response I got. It works as you assumed:
The
/v1/files/publish-file/...endpoint translates to a publish endpoint in the server so thatcustom_message_typewill work exactly like thetypeparameter. No change
d8a08f3 to
458e1a6
Compare
|
@pubnub-release-bot release |
|
🚀 Release successfully completed 🚀 |
feat(message-type): add custom message type support
Add custom message type support for the following APIs: publish, signal, share file, subscribe, and history.