Symbol props / HOCs ?

[ampled]

Playground: https://svelte.dev/playground/c601b2e8051845ec89295630eb5eea86?version=5.25.3

Since Svelte 5 components are functions now, I've been experimenting with creating "Higher Order Components" / component wrapper functions that can augment props.
The goal I'm trying to achieve is creating a component that can receive any prop and also be able to receive some configuration without "reserving" a prop name (and not use context) so I've come up with passing extra props using a symbol key.

So when doing stuff that is undocumented I'm asking myself "is this bad?" and "can this break something" ?
Hoping to get some input on that.

[Ocean-OS]

Since the order, type, etc of arguments passed to a component function could change without warning (since it would be an internal change), I wouldn't recommend creating functions that depend on them.

[ampled]

Oof, okay, so this isn't future-proof.

What about the symbol keys as props?

[brunnerh]

They might be unilaterally hijacked for attachments, unless someone stops that (or Rich sees reason 😄).

[ampled]

No problem, kinda:

https://svelte.dev/playground/2c883ba649db4307b009a37327fb5e63?version=pr-15000 😎

I cant spread rest-props to the ul-element because it's trying to call any symbol prop as an attachment function buuuut I feel like that can be worked around. If Svelte ignored non-function symbol props passed to elements it wouldn't be a problem at all.

I realize my use-case is probably very niche here (I was planning to implement something cool for my library with symbol props ) so I'm fine with whatever gets implemented.