Unclear > in Svelte 5 migration guide

[adamshand]

Describe the bug

In "why we did this?" under "multiple event handlers" there are a bunch of >.

I assume they are typos, but if not their meaning is unclear to me.

It was always possible to use component callback props, but because you had to listen to dom events using on:, it made sense to use createEventDispatcher for component events due to ❓> syntactical consiscency. Now that we have event attributes (onclick), it’s the other way around: Callback props are now the more sensible thing to do.

The removal of event modifiers is arguably one of the changes that seems like a step back for those who’ve liked the shorthand syntax of event modifiers. Given that they are not used that ❓> frequently, we traded a smaller surface area for more explicitness. Modifiers also were inconsistent, because most of them were only useable on Dom elements.

Multiple listeners for the same event are also no longer possible, but it was something of an anti-pattern anyway, since it impedes readability: if there are many attributes, it becomes ❓> harder to spot that there are two handlers unless they are right next to each other. It also implies that the two handlers are independent, when in fact something like event.❓> stopImmediatePropagation() inside one would prevent two from being called.

Reproduction

.

Logs

.

System Info

.

Severity

annoyance

[adamshand]

Also consiscency should be consistency.

[brunnerh]

Probably a side effect of moving lines around, those "why we did this?" blocks are formatted as Markdown blockquotes so each line starts with a >.