Trying to highlight some code in a `leptos` application - can't get errors as HTML tags?!

[lyric goblet]

Hey there!

I am doing this right now:

    use typst::syntax::highlight_html;
    use typst::syntax::parse;

    let sn = parse(&code);
    let html = highlight_html(&sn);

My problem: if the typst code contains errors, the html doesn't contain any errors.

My assumption, that's because ```rust
fn highlight_html_impl(html: &mut String, node: &LinkedNode) {
let mut span = false;
if let Some(tag) = highlight(node) {
if tag != Tag::Error {
span = true;
html.push_str("<span class="");
html.push_str(tag.css_class());
html.push_str("">");
}
}
...

Error explicitly doesn't return any html-tag.

So, how can I get the error like in `typst.app`?

Trying to highlight some code in a leptos application - can't get errors as HTML tags?!

[oblique trout]

Multiple things to unpack here. From a quick look, your assumption is correct.
If you only want to detect syntax errors, the parse function in typst-syntax is probably the way to go
If you want all kind of compiler errors, you will need to go with the compile function in the typst crate.
The last one is a lot more work to get going, as you will need to provide a World implementation

[lyric goblet]

Hm, thanks... I have my own WorldWrapper, not that difficult, especially with https://github.com/tfachmann/typst-as-library

[lyric goblet]

If you only want to detect syntax errors, the parse function in typst-syntax is probably the way to go

is not it though, because that's what I am using... I mean, it gives you the error, but then when you translate it to HTML, it's ignored

Maybe I'll have to write my own syntax-highlighting, although that would be a shame and wasted energy

[oblique trout]

Mh, I think I understand the problem now

You probably don't get around writing your own highlighter then
But it shouldn't be too hard to just copy the existing one and editing it to handle errors, right? Maybe it would even be nice to upstream these changes to Typst itself

I must say I find it especially weird/funny that a CSS class for an error is explicitly defined but then not used 😅

[lyric goblet]

Exactly, that's why I thought I had missed something

[tranquil moat]

Not sure what my thinking there was. Maybe I disabled it because I wanted to frequently highlight half-wrong things like .foo(..) in the docs and everything turned red all the time.