aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/highlighting.ts
Commit message (Collapse)AuthorAgeFilesLines
* removed `type.alias`Omer Ben-Amram2019-12-141-0/+1
|
* added decorationsOmer Ben-Amram2019-12-141-0/+6
|
* Code: enable prettier trailing commasLaurențiu Nicola2019-12-091-8/+8
|
* Code: bump depsLaurențiu Nicola2019-12-081-3/+4
|
* underline mutable bindingsAleksey Kladov2019-07-191-27/+34
|
* highlight mutable variables differentlyEkaterina Babshukova2019-07-181-0/+1
|
* Make rainbows optionalPascal Hertleif2019-05-271-5/+6
|
* Semantic highlighting spikePascal Hertleif2019-05-271-3/+42
| | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* Improve highlighting of name refsLaurențiu Nicola2019-05-231-1/+6
|
* Address feedbackLaurențiu Nicola2019-05-211-3/+2
|
* Use ThemeColor and add support for light themesLaurențiu Nicola2019-05-211-13/+22
|
* highlight macro identsAleksey Kladov2018-12-281-1/+2
|
* Remove error publishing through publishDecorationsAdolfo Ochagavía2018-10-101-7/+0
|
* Run prettier on all filesDaniel McNab2018-10-081-17/+28
|
* Fix remaining tslint suggestionsAdolfo Ochagavía2018-10-081-31/+35
|
* Apply tslint suggestions, round oneAdolfo Ochagavía2018-10-071-33/+33
|
* Refactor vscode extensionAdolfo Ochagavía2018-10-071-0/+78