[commands] provide command args directly #107
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.
Why?
Currently, we make you wrap every single command, even nested ones. The invocation looks like
It would be nice to not have to wrap things in Command(). The client library can simply do it for you.
I didn't remove Command() because I think it's actually a good pattern for composing larger commands. Also, backwards compatibility!
What changed
add
, and the oldregister
/registerCreate
methods all accept raw objects in addition to the wrappedCommand(...)
. When you don't wrap your command objects, we do it for you{[CommandSymbol]: true}
once we wrap, just to make sure we're not doing it twiceTest plan
hey
in the commandbar, which returnshello
andhola