-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Add VoidCallbackAction and VoidCallbackIntent #103518
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 VoidCallbackAction and VoidCallbackIntent #103518
Conversation
goderbauer
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
| /// | ||
| /// Must not be null. |
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.
Isn't this still true?
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.
Yes, but it's non-nullable, so I assume that gives enough implicit documentation that it can't be null.
I realize that someone could be using a weak nullability app, though. I'll reinstate it.
93932aa to
f09d29f
Compare
|
This pull request is not suitable for automatic merging in its current state.
|
Description
This adds a simple
VoidCallbackActionandVoidCallbackIntentthat allows configuring an intent that will invoke a void callback when the intent is sent to the action subsystem. This allows binding a shortcut directly to a void callback in aShortcutswidget.I also added an instance of
VoidCallbackActionto the default actions so that simply binding a shortcut to aVoidCallbackIntentworks anywhere in the app, and you don't need to add aVoidCallbackActionat the top of your app to make it work.Tests