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
Add interactivity pointer #1526
Add interactivity pointer #1526
Conversation
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.
Yay thanks for tackling this! Left some comments for ya.
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.
Okay! Some documentation comment suggestions here to wrap up, but the changes to the types are looking good to me.
Let's branch next-gen
off main and point this branch to merge to that. That way we'll be all set up for cutting the beta release of web-api
.
Summary
Events like
block_action
,views_*
events that are sent with interactivity payloads aka (function, function_data) will no longer containtrigger_id
but instead a new field calledinteractivity_pointer
. The motivation is to move away from the legacy term "trigger" as it doesn't actually refer to the 2.0 concept of trigger.This doesn't affect those same events if they are not sent with interactivity payload data (aka regular 1.0 block actions and views events), so there shouldn't be an impact on existing devs / apps.
Requirements (place an
x
in each[ ]
)