fix: Add kwargs to add_action wrapper#531
Open
beatreichenbach wants to merge 1 commit intospyder-ide:masterfrom
Open
fix: Add kwargs to add_action wrapper#531beatreichenbach wants to merge 1 commit intospyder-ide:masterfrom
beatreichenbach wants to merge 1 commit intospyder-ide:masterfrom
Conversation
0fc985c to
508b392
Compare
508b392 to
8920bed
Compare
Member
|
Hi @beatreichenbach thank you for giving that issue a check! The summary of possible signatures that you mention makes sense to me 👍 For completness, checking to the different bindings and got the following signatures when checking
So seems like one missing signature from the ones listed in the OP is passing a |
Contributor
Author
|
Okay thanks, I'll add a check for all of them and try to refactor that |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds the kwargs back to the add_action function and should hopefully fix #472.
However, before proceeding, I would like to add tests for all cases. I'm a bit unsure what cases should be supported. Does this cover everything?