Support for ligatures in JavaScript?

[FezVrasta]

Hi, I see that if I write => it gets converted in:

<span class="token operator">=</span>
<span class="token operator">></span>

But this breaks the ligature of the font I'm using (Fira Code).

Could it be possible to group together tokens of the same type to allow ligatures?
Ideally the markup should be:

<span class="token operator">=></span>

[Golmote]

Hi, what language are you highlighting?

[FezVrasta]

JavaScript.

[Golmote]

Thanks for reporting. This should be fixed now.

[hax]

@Golmote Could you publish a new version on npm?

[ManuelRauber]

Is this really fixed?

Seems not to work for C# code

[RunDevelopment]

Well, it is fixed in JavaScript but not C#.

The title is was kind of ambiguous.

[dsvensson]

@Golmote Same applies to Rust, :: at least.. perhaps more.

[RunDevelopment]

@dsvensson Does this also apply for other Rust operators?
I found that the .. operator has the same problem and wanted to ask whether there are other multi-character operators in Rust.

Edit: Nvm. I tested .. with the wrong language...

[dsvensson]

@RunDevelopment Nice... the documentation actually has a complete table of all operators, https://doc.rust-lang.org/book/appendix-02-operators.html

[VFDan]

=> isn't the only operator in JavaScript with ligatures; ?? exists, and many others. I think that this could break the way Prism works though... Maybe groups of token operators could be put into the same group.

This is ridiculous:

[RunDevelopment]

@VFDan
Prism generally captures operators as a whole even if composed of several characters. E.g. ..., =>, and ?? will all be matched as one token. This requires some maintenance but is also more useful when processing Prism's token stream because Prism has some real understanding of the code. A neat little side-effect is that font ligature is natively supported.

Point is: ligatures breaking is usually just a sign that Prism tokenization isn't correct.