-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Satisfy revised MSC4157 #92
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.
I guess this is the PR where we will do the renaming to delay
and add the capabilitie names.
Yes, I'll be pushing more commits here, for the rest of the revisions to MSC4157. I'll mark it as draft until that's done. |
timeout to delay & futureId to delayId
Use type checks to disallow arbitrary string values as actions
The last batch of commits includes the widget API action for updating delayed events, which is the last thing that was missing to satisfy the MSC. This should be good to go now. |
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.
This looks all as expected!
Co-authored-by: Timo <[email protected]>
This is part of the recent revisions to MSC4140/4157.
Another PR will be made for adding a widget capability for using the now-authenticated endpoint for sending/canceling/refreshing a future.This PR also includes the widget action & capability for sending/canceling/refreshing a delayed event.Signed-off-by: Andrew Ferrazzutti [email protected]