separate code spans

[Rich-Harris]

alternative to #560. This is just a test, we would need to make the same change in the svelte and kit repos

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kit-svelte-dev	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2024 7:59pm
learn-svelte-dev	🛑 Canceled (Inspect)			Oct 23, 2024 7:59pm
omnisite	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2024 7:59pm
svelte-5-preview	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2024 7:59pm
svelte-dev	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Oct 23, 2024 7:59pm

[Conduitry]

Presumably not strictly necessary here. I don't know whether this still makes sense to do anyway.

[Rich-Harris]

I think we may as well be consistent

[dummdidumm]

can we automate this somehow? Like, the markdown renderer sees "there's a ` followed by a / followed by a `, I'm putting a space inbetween that ". I feel like we're going to make this mistake over and over again if we're not super careful

[Conduitry]

Automating this via the renderer sounds good, if we can make it work properly. As Rich's initial mass-find-replace indicated, there are a lot of false positives if you're just looking for those three specific characters in a row. But maybe it might more doable in a renderer if we have access to more AST-y stuff.

[Rich-Harris]

The first question to answer is whether we like this change:

Personally I think it's actually an improvement, but want to be sure others agree.

As for automating: are we imagining a warning or actually transforming it? Not sure off the top of my head if there's a single place to put that logic

[dummdidumm]

Actually transform it.
Agree it looks better