Component event and prop names too permissive

[pushkine]

Event and prop names accept all characters but space, quotes, > and =

<Component on::::\\\\!!!}}]]{{{function(){return`hello_world`}}{]]])(((\ \\````::\**\{{{}}}}}}<<<<<<Component />

component = new Component({
	props: {
		"\\\\````::\\**\\{{{}}}}}}<<<<<<Component": true
	}
});

component.$on(":::\\\\\\\\!!!}}]]{{{function(){return`hello_world`}}{]]])(((\\", 
/*function_return_hello_world_handler*/ ctx[0]);

https://svelte.dev/repl/8bff2976db80403db1affa9138c3e8dd?version=3.31.2

[dummdidumm]

Agree with that. From a tooling perspective it would be ideal to only allow alphanumeric characters and $_ and maybe -

[Conduitry]

Is this actually causing a bug, or is it just unsightly?

[dummdidumm]

From a tooling perspective it causes some problems because JSX/TSX, which code is transformed to for intellisense features, is more restrictive, but I've not yet encountered an actual bug. So from my point of view it would be more of a "more well defined" thing.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dummdidumm]

I still think this would be good to make more strict. It would make tooling easier. Strictly speaking it's probably a breaking change though.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dummdidumm]

Thinking about this differently now. Still would be cool but many libraries take advantage of the more permissive nature of props and events and added things like - to their prop names. Also some libraries work around current limitations of event bubbling by using special characters that are not ! to simulate event modifiers.

[dummdidumm]

Now thinking that it's not worth the hassle - the language tools argument I brought up back in the day is no longer relevant.

[Rich-Harris]

we decided to not worry about this. it is a potential footgun, but it's also a potential escape hatch, and escape hatches should be left unlocked

[Malix-Labs]

What would be an example where such escape hatches would be required?

[Rich-Harris]

The nature of escape hatches is that it's hard to predict when you need them!