-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
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
Need more variables in inline statement #1945
Comments
Well, after a researching of src codes, i found there is no variable(even |
Thanks, I think something like |
got it |
Add $arguments variable in component events inline statement #1945
Does If I do:
It catches only the first argument. So somehow I need to catch all events and seemed that $arguments is the best solution. |
Oh Ok I found that $arguments do not exists but |
Currently only$event
variables is provided, and it represents the first argument this handler being called(DOM events in most case). But it is not suitable for custom vm events, especially with multi arguments.eg.
I suggest add a more flexible variable(such as
$
or$$
) to represents all arguments, so we can get any argument by@my-event="handle($[0], $[1])"
.For convenient, we can provide
$0
-$9
to represents corresponding arguments like Bash.@yyx990803 , if you agree with me and think this is necessary, please let me pull a PR for this
The text was updated successfully, but these errors were encountered: