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

TypeScript Syntax Highlighting Broken #56706

Closed
mattmazzola opened this issue Aug 17, 2018 · 8 comments
Closed

TypeScript Syntax Highlighting Broken #56706

mattmazzola opened this issue Aug 17, 2018 · 8 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Milestone

Comments

@mattmazzola
Copy link
Member

Issue Type: Bug

I updated to latest version 1.26.1 and now code that was viewed properly before no longer has proper syntax highlighting

image

VS Code version: Code 1.26.1 (493869e, 2018-08-16T18:37:28.532Z)
OS version: Windows_NT ia32 10.0.17134

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (12 x 3492)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 31.91GB (16.45GB free)
Process Argv C:\Program Files (x86)\Microsoft VS Code\Code.exe
Screen Reader no
VM 0%
Extensions (10)
Extension Author (truncated) Version
bracket-pair-colorizer Coe 1.0.59
gc-excelviewer Gra 2.1.25
code-beautifier mic 2.1.0
dotenv mik 1.0.1
python ms- 2018.7.1
csharp ms- 1.15.2
PowerShell ms- 1.8.3
debugger-for-chrome msj 4.8.2
code-spell-checker str 1.6.10
vscode-adaptivecards tom 1.1.3
@gluons
Copy link

gluons commented Aug 18, 2018

Subscribed!

I also face the same problem. Colors look weird and inconsistent.

default

@mjbvz
Copy link
Collaborator

mjbvz commented Aug 20, 2018

Please share the text of the code along with screenshots

@mjbvz mjbvz added the info-needed Issue requires more information from poster label Aug 20, 2018
@mattmazzola
Copy link
Member Author

mattmazzola commented Aug 20, 2018

Here is a link to the file I had screenshot from above:
https://github.com/Microsoft/ConversationLearner-SDK/blob/c0c4f4a511b754c595e6368fcbd7e6b585665898/src/CLRunner.ts

Interestingly I noticed the syntax highlighting on this file is also broken in almost the same locations with same affects on GitHub as it is in VSCode. Perhaps this can be clue to fix the issue if they use the same dependency for computing this.

Notice it starts to break at (colors start to be mismatched):
https://github.com/Microsoft/ConversationLearner-SDK/blob/c0c4f4a511b754c595e6368fcbd7e6b585665898/src/CLRunner.ts#L166

(Notice the return statement just below is not red anymore)

And is completely broken here (all the same color):
https://github.com/Microsoft/ConversationLearner-SDK/blob/c0c4f4a511b754c595e6368fcbd7e6b585665898/src/CLRunner.ts#L259

@mjbvz
Copy link
Collaborator

mjbvz commented Aug 20, 2018

Seems fixed in latest insiders build
screen shot 2018-08-20 at 6 14 50 pm

Let me know if you still see this issue in the current insiders

@mjbvz mjbvz closed this as completed Aug 20, 2018
@mjbvz mjbvz added *not-reproducible Issue cannot be reproduced by VS Code Team member as described and removed info-needed Issue requires more information from poster labels Aug 20, 2018
@mjbvz
Copy link
Collaborator

mjbvz commented Aug 20, 2018

@gluons Opened microsoft/TypeScript-TmLanguage#653 for that

In the future please open a separate issue as it makes tracking and management easier

@mattmazzola
Copy link
Member Author

Hmm. I just downloaded the insiders and still see the error. Even disabled all extensions. Was the version below the one you were using? Is there a better way for me to verify?

VS Code version: Code - Insiders 1.27.0-insider (6e55926, 2018-08-20T08:36:52.887Z)
OS version: Windows_NT x64 10.0.17134

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz (12 x 3492)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 31.91GB (15.03GB free)
Process Argv C:\Users\mattm\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe
Screen Reader no
VM 0%
Extensions: none

@mjbvz mjbvz added bug Issue identified by VS Code Team member as probable bug and removed *not-reproducible Issue cannot be reproduced by VS Code Team member as described labels Aug 20, 2018
@mjbvz mjbvz added this to the August 2018 milestone Aug 20, 2018
@mjbvz mjbvz added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Aug 20, 2018
@mjbvz
Copy link
Collaborator

mjbvz commented Aug 20, 2018

Oh yeah format on paste fixes this if you copy it from github. Caused by a trailing space messing up syntax highlighting. Opened microsoft/TypeScript-TmLanguage#654 to track this

mattmazzola added a commit to microsoft/ConversationLearner-SDK that referenced this issue Aug 20, 2018
There is current bug with syntax highlighting on TypeScripot files which have trailing white space.

microsoft/TypeScript-TmLanguage#654
microsoft/vscode#56706 (comment)
mattmazzola added a commit to microsoft/ConversationLearner-SDK that referenced this issue Aug 20, 2018
There is current bug with syntax highlighting on TypeScripot files which have trailing white space.

microsoft/TypeScript-TmLanguage#654
microsoft/vscode#56706 (comment)
@octref octref added the verified Verification succeeded label Aug 30, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants