`$props` aliasing allows invalid names

[ottomated]

Describe the bug

This is syntactically valid:

const { '=;123': alias } = $props();

but obviously, this is not:

<Component =;123="foo" />

Svelte should throw an error on invalid prop names here.

Reproduction

REPL

Logs

No response

System Info

n/a

Severity

annoyance

[dummdidumm]

Related #5903

[FoHoOV]

It allows something like this. Maybe a naming convention which makes sense (not this obviously) is using this "feature" somewhere. I think

<Component "=;123"={"foo"} />

should work though if this is going to be allowed.

[7nik]

But you can easily pass a prop with any name using spreading:

let props = { "=;123": 42 };

<Component {...props} />

[7nik]

I think

<Component "=;123"={"foo"} />

should work though if this is going to be allowed.

It will break the "compatibility" with HTML, and no one uses such names because they only cause headaches in other places. Those who do need it can still use prop spreading, prop aliasing, rest props, etc.

[ottomated]

I think it's fine to allow some special characters here, but definitely not =. <Component ;123="foo" /> surprisingly does compile.

[7nik]

The HTML standard disallows space, ", ', >, /, =, and obviously noncharacters. Anything other can be used in the attribute name.

[brunnerh]

In addition, given that spreading works with anything, I don't think anything should be done here.