Skip to content

Conversation

@jguz-pubnub
Copy link
Contributor

@jguz-pubnub jguz-pubnub commented Oct 16, 2024

feat(message-type): add custom message type support

Add custom message type support for the following APIs: publish, signal, share file, subscribe, and history.

Copy link
Contributor

@parfeon parfeon left a 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?,
Copy link
Contributor

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.

Copy link
Contributor Author

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 that custom_message_type will work exactly like the type parameter. No change

@jguz-pubnub jguz-pubnub force-pushed the feat/add-message-type2 branch from d8a08f3 to 458e1a6 Compare November 18, 2024 09:50
@jguz-pubnub jguz-pubnub changed the title Add support for custom message type Add custom message type support Nov 18, 2024
@jguz-pubnub
Copy link
Contributor Author

@pubnub-release-bot release

@jguz-pubnub jguz-pubnub merged commit 022aa54 into master Nov 18, 2024
10 checks passed
@jguz-pubnub jguz-pubnub deleted the feat/add-message-type2 branch November 18, 2024 11:01
@pubnub-release-bot
Copy link

🚀 Release successfully completed 🚀

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