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
FWIW, should be a worthwhile change, especially since for long term compatibility, it should be supported in Svelte 4,. See: sveltejs/svelte#8457 😄
some things are hard to auto-configure, like attribute hyphen preferences or whether or not setting a property should reflect back to the attribute. This is why <svelte:options customElement={..}> can also take an object to modify such aspects. This option allows to specify whether setting a prop should be reflected back to the attribute (default false), what to use when converting the property to the attribute value and vice versa (through type, default String, or when export let prop = false then Boolean), and what the corresponding attribute for the property is (attribute, default lowercased prop name). These options are heavily inspired by lit: https://lit.dev/docs/components/properties. Closes sveltejs/svelte#7638, fixes sveltejs/svelte#5705
Would love the ability to support the following:
Where the element attribute
foo-bar
is automatically translated to its camelCase counterpart:fooBar
, making it available inCustomElement.svelte
as:Looks like @wagich already did some work to address this particular use case in this specific commit already: b95dd6c
The text was updated successfully, but these errors were encountered: