Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broke ligatures highlighting with Bracket pair colorization enabled #1586

Open
len0xx opened this issue Aug 13, 2022 · 2 comments
Open

Broke ligatures highlighting with Bracket pair colorization enabled #1586

len0xx opened this issue Aug 13, 2022 · 2 comments
Labels
bug Something isn't working upstream

Comments

@len0xx
Copy link

len0xx commented Aug 13, 2022

Describe the bug

I have Svelte for VSCode extension installed, 'Fira Code', monospace set as the Font Family and Bracket Pair Colorization enabled in VSCode settings. When VSCode updated the last time to 1.70.1 few days ago, the bug showed up. In all of my svelte files in the script tag with lang set to "ts" arrow function syntax highlighting is kind of broken: the first symbol of the arrow (=) is colorized while the second (>) is not

Reproduction

  1. Set Font Family to 'Fira Code', monospace
  2. Enable Bracket Pair Colorization
  3. Enable ligatures
  4. Create a svelte file
  5. Add the following code to the file:
<script lang="ts">
    const a = (id: number) => id + 2
</script>

Expected behaviour

I expect the whole arrow to be the same color as it was before the recent VSCode update

System Info

  • OS: macOS arm64 21.4.0
  • IDE: VSCode 1.70.1

Which package is the issue about?

Svelte for VS Code extension

Additional Information, eg. Screenshots

photo_2022-08-13 15 42 16

@len0xx len0xx added the bug Something isn't working label Aug 13, 2022
@PatrickG
Copy link
Contributor

Seems to be a VSCode problem.
microsoft/vscode#157322

@len0xx
Copy link
Author

len0xx commented Aug 13, 2022

Seems to be a VSCode problem. microsoft/vscode#157322

I was hestitating between reporting it to VSCode repo and this repo. Looks like its a VSCode issue actually. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream
Projects
None yet
Development

No branches or pull requests

3 participants