-
Notifications
You must be signed in to change notification settings - Fork 97
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
Calling static command service methods with NamedCommand Arguments #1165
Comments
This is known bug: #980 |
Alright, didn't know that. Gonna close this issue then. |
exyi
added a commit
that referenced
this issue
Oct 14, 2021
The parameters were passed in a very weird way, now it works similar to command bindings - even when command is not a lambda function, it is wrapped in a lambda function. Then, the lambda function gets parameters assigned directly, so the lambda syntax is essentially eliminated. This back and forth is kinda needed to align how it works in case command is specified as plain expression and when it's specified as lambda function. resolves #980, #1165
exyi
added a commit
that referenced
this issue
Oct 16, 2021
The parameters were passed in a very weird way, now it works similar to command bindings - even when command is not a lambda function, it is wrapped in a lambda function. Then, the lambda function gets parameters assigned directly, so the lambda syntax is essentially eliminated. This back and forth is kinda needed to align how it works in case command is specified as plain expression and when it's specified as lambda function. resolves #980, #1165
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if I am doing something wrong but I am unable to call static command service method with
NamedCommand
arguments.View:
Call from js:
I get this console error after calling the command:
When I separate the the commands into two so I just assign the
hotSpotId
to a view model property in one static command and call the static command service method without arguments fromNamedCommand
in the second one everything works fine.I also tried using command that calls a method on view model with
NamedCommand
arguments and it wasn't called at all either.The text was updated successfully, but these errors were encountered: