Skip to content
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 note about no-op for global context action #293

Open
fidgetingbits opened this issue Jul 17, 2024 · 0 comments
Open

Add note about no-op for global context action #293

fidgetingbits opened this issue Jul 17, 2024 · 0 comments

Comments

@fidgetingbits
Copy link
Contributor

fidgetingbits commented Jul 17, 2024

This was something I was looking for awhile back as well, and it just came up on slack recently, so likely worth documenting:

What is the recommended way to define an action that is a no-op when in global context, but does something in a specific context? I believe Talon has some no-op checking code so that it can complain if you call an action that you forgot to implement in a given context cc/ Andreas Arvidsson

Response from Andreas

Personally I'm a fan of actions.skip(). I think the intent there is very clear both to a human reader and to Talon.

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

No branches or pull requests

1 participant