lambda in staticCommand can not pass arguments to server methods #980
Comments
|
We need to do this change in DotVVM 4.0 because it depends on dropping the support for IE11 (we need to use async/await in JS expressions). |
|
Since we have rewritten promises to async/await calls, we should add tests for this case. (referring to #1105) |
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
{staticCommand: (int x) => s.Method(x)}produces invalid expression - the argument is declared after theMethodis invoked, which leads to JS error.The text was updated successfully, but these errors were encountered: