QuasiQuotes

[dpwiz]

They can mean just about anything so their contents should be treated either as plain text or a string literal.

There is a list of reserved names for quotes that should remain as Haskell code.

[marcotoniut]

It would be nice if language-haskell would somehow allow for extended syntax highlighting on QuasiQuote expressions.

[vaclavsvejcar]

Wondering if there are any plans for this issue? Any chance to have quasiquotes somehow visually distinguished?

[JustusAdam]

My intuition is that it is possible, but I don't have the time to work on it. If you want to give it a shot go ahead.

AFAIK there are standard quasi quoters for declarations and expressions. A multi line matcher could be used for the quote brackets and then an include for the expression or declaration rules would add the desired highlighting.

[poscat0x04]

Right now QuasiQuotes are incorrectly linted if there are keywords in it.

[nilehmann]

Hi, I'm dealing with the same problem. Why is this marked as enhancement and not as bug?

[sheaf]

I've made a simple change so that the entire quasi-quotation is only given the meta.quasi-quotation scope, with no Haskell highlighting.

The "enhancement" part of the bug pertained to the ability to highlight the inside of the quasi-quote depending on the quasi-quoter, e.g. highlight a JSON quasi-quotation using JSON rules, or highlight the different types of Haskell quasi-quotations (type/expression/etc) using the appropriate rules.

[nilehmann]

@sheaf, that makes sense. And thank you for implementing the quick fix 😃, the highlighting inside of quasiquotes was killing me.

[sheaf]

I also implemented simple Haskell highlighting for the expression, pattern, declaration and type quasi-quoters. Anything more than that starts getting a bit tricky unfortunately.

[nilehmann]

Should 3.1.0 have these changes? I just updated but I don't see any of the new scopes :S. What could I be doing wrong?

[sheaf]

The changes are indeed part of 3.1.0. (I just checked to confirm).

If you press Ctrl+Shift+P and bring up Developer: Inspect Editor Tokens and Scopes, you should see the meta.quasi-quotation.haskell scope over the whole quasi quotation, and then the appropriate highlighting in case it's a Haskell quasi-quotation.

[nilehmann]

Yeah, I was exactly doing that and I didn't see the scope. There's must be something on my end (maybe conflicting with another extension?). I'll try with a clean vscode setup when I have time and see...

[sheaf]

The other thing you can try is to manually revert to an older extension (Install another version... after pressing the settings gear next to the extension in the list of extensions), and then update again to 3.1.0.

[JustusAdam]

Ah that's my fault. Apparently I forgot to rebuild the JSON before publishing. I really need to make that automatic.

[nilehmann]

Yup, working for me in 3.2.0 now. On the bright side I learned a lot about scopes, textmate and stuffs along the way 😁

[JustusAdam]

Run while you still can 😝 😆

[jbpotonnier]

Would it be possible to mark the quasi quote content with the scope meta.embedded.block.{nameOfQuasiQuote} ?

For example, the content of

[hsx|
        <div>
        ...
        </div>
    |]

would be marked as meta.embedded.block.hsx

If I got it correctly, it would then be possible to provide separate extensions for any quasiquote syntax.

[sheaf]

@jbpotonnier Thanks for the suggestion, which I've implemented in 4c9905e. So we have:

[hsx| ... |]
      ^^^ meta.embedded.block.hsx

[Qualifier.hsx| ... |]
                ^^^ meta.embedded.block.hsx

Let me know if that works for you.

[poscat0x04]

Currently (version 3.3.0), quasi-quotations will break the linting of the code after it if there are no letters in between the parenthesis:

[sheaf]

@poscat0x04 Fixed the issue with empty quasi-quotations in 150c9c5, thanks for the bug report.