kebab case for custom elements about attractions

[atomkirk]

I guess I could just fork the repo and rename all the props to be all lowercase then build it myself? 🤔

[atomkirk]

maybe a strategy like this could also be used
https://github.com/oranmor/svelte-custom-element-dash-properties-example

specifically:

https://github.com/oranmor/svelte-custom-element-dash-properties-example/blob/master/src/MyCustomComponentWrapper.js

[atomkirk]

For context, I want to use this component lib with Phoenix Liveview. I think making this lib very consumable as custom elements greatly increases the market for it since it can be used by any front-end framework.

[aabounegm]

That indeed seems like a nice solution for the prop naming issue, but unfortunately there is a bigger problem at hand. Currently, Svelte does not correctly output a custom element for nested components. Unfortunately, we do a lot of component reuse in the library and it's not very feasible to migrate all the usages to custom elements, so until sveltejs/svelte#3520 is resolved, custom elements are not supported and we intend to remove the docs page in the next release.

[atomkirk]

Ahhhhh. Thank you that answer!!