You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you think it makes sense to add syntax highlighting support for markdown code?
Also, a more useful feature. Does it maybe make sense to add diff support in markdown? This'd help to easily display inline suggestions of code than should be removed + added. Sort of like GitHub suggestions or diff markdown. For example: 👇
const foo = "bar";
- type a = (typeof);+ type a = typeof foo;
The text was updated successfully, but these errors were encountered:
Yes, I think we should do syntax highlighting and prettifying for all the code snippets. I.e. you should be able to view {0}, {1}, etc all pretty, with syntax highlighting.
This is complicated by the fact that TS sometimes has 'and 2 more' in their code snippets. But a smart fella like you could work around that, I'm sure (perhaps wrapping it in a comment, then prettifying it).
I kind of like the idea of diffing (I assume you mean in the body) but not as much as I like the idea of integrating shiki-twoslash for really bringing out the errors. We're using it in the new XState docs, I'm sure it would work great for the site.
Hey 👋
Do you think it makes sense to add syntax highlighting support for markdown code?
Also, a more useful feature. Does it maybe make sense to add diff support in markdown? This'd help to easily display inline suggestions of code than should be removed + added. Sort of like GitHub suggestions or diff markdown. For example: 👇
The text was updated successfully, but these errors were encountered: