-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Using an action twice throws "same attribute" error #5516
Comments
Do you want to have the same script run twice on the node? |
@peopledrivemecrazy @antony I have a similar question: Is it possible to use an action twice on the same node? I have written a small animation function that looks something like this: <div use:animate={{trigger: scrollY, opactiy: {start: 0, end: 200, from: 0, to: 1}}} /> It would be very helpful for me if I could use them several times on same element, so i can create |
Heya,
It is not. Why not make your action take an array?
On Sun, 18 Oct 2020 at 18:36, Niklas Grewe ***@***.***> wrote:
@peopledrivemecrazy <https://github.com/peopledrivemecrazy> @antony
<https://github.com/antony> I have a similar question: Is it possible to
use an action twice on the same node? I have written a small animation
function that looks something like this:
<div use:animte={{trigger: scrollY, opactiy: {start: 0, end: 200, from: 0, to: 1}}} />
It would be very helpful for me if I could use them several times on same
element.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABVORP4RNL2O5WJLQUJVYTSLMRQXANCNFSM4SLOAYYQ>
.
--
…________________________________
ꜽ . antony jones . http://www.enzy.org
|
You can use it twice like this:
|
This works great. |
As of 3.32.0, you can now have multiple instances of the same action - https://svelte.dev/repl/01a14375951749dab9579cb6860eccde?version=3.32.0 |
This works fine good job @pushkine |
https://svelte.dev/repl/01a14375951749dab9579cb6860eccde?version=3.29.0
The text was updated successfully, but these errors were encountered: