Signal for more generic function call interceptions #5254
Merged
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.
Recently we've got a bunch of PRs adding signals that are pretty much just providing a way to tamper with the arguments of certain function calls. And while we're open to accepting such PRs, I had the feeling that this was getting a bit messy, so I thought about providing a more standard way to handle this. While it would still require PRs to adjust a function call in order to provide this type of hook, it'd be much simpler than building a dict and updating it based on the signal return values...
Feedback welcome!
Also, for our UN colleagues @OmeGak @vasantvohra @SegiNyn, maybe you can have a look as well and see if you'd find this useful? Here's an example on how I'd use this instead of the recently-added
draw_item_on_badge
signal:and the plugin could be doing something like this then: