You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both Vue and Alpine have this weird syntax where events get preceded by @. I'm using htm in a library for templating. Preact is more of an implementation detail, and not really exposed to users. I'm seeing someone who uses alpine on the rest of the page and wants an event handler that's handled by alpine in that template. Unfortunately the shorthand syntax doesn't seem to work due to setAttribute.
A reproduction is:
import{render}from"preact";import{html}from"htm/preact";// does workrender(html`<divx-data="{ open: false }"><button@click="open = !open">Expand</button><spanx-show="open"> Content...</span></div> `,document.body);
(workaround is replacing @ to x-on:, but our user wasn't aware of this)
I'm guessing no workaround will be possible as it's actually setAttribute throwing, but I wonder if you know something that would avoid users changing their expectations.
The text was updated successfully, but these errors were encountered:
Haroenv
changed the title
Find a way to allow "@" in attribute
Find a way to allow "@" in attribute?
Jan 17, 2023
Both Vue and Alpine have this weird syntax where events get preceded by
@
. I'm using htm in a library for templating. Preact is more of an implementation detail, and not really exposed to users. I'm seeing someone who uses alpine on the rest of the page and wants an event handler that's handled by alpine in that template. Unfortunately the shorthand syntax doesn't seem to work due tosetAttribute
.A reproduction is:
(workaround is replacing
@
tox-on:
, but our user wasn't aware of this)sandbox: https://codesandbox.io/s/festive-wildflower-qeugtn?file=/src/index.js
other relevant issues:
alpinejs/alpine#1235
alpinejs/alpine#396
algolia/instantsearch#5435
I'm guessing no workaround will be possible as it's actually setAttribute throwing, but I wonder if you know something that would avoid users changing their expectations.
The text was updated successfully, but these errors were encountered: