Repository navigation
feat: custom actions pass their data to registerCustomAction - #187
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Custom actions clicked in chat messages and message cards now reach
Gleap.registerCustomActionwith their data: the callback gets{ name, shareToken, data }.GleapFrameManager: forwards the Messenger's newactionDatafield ofrun-custom-actionasdata(only when present).index.d.ts: the callback's action type listsdataandshareToken.Backward compatible both ways: older Messenger builds don't send
actionData, older SDKs ignore it. The Messenger side is GleapSDK/Messenger-App#264. iOS and Android get the same field with the next synced SDK release.Tested: jest suite passes.
🤖 Generated with Claude Code