Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Implement syntax highlighting for doctests | Leander Tentrup | 2020-06-08 | 1 | -46/+80 |
| | |||||
* | Add highlight support for unsafe fn calls and raw ptr deref | Paul Daniel Faria | 2020-06-02 | 1 | -1/+24 |
| | |||||
* | Merge #4664 | bors[bot] | 2020-05-31 | 1 | -77/+84 |
|\ | | | | | | | | | | | | | | | 4664: Generate feature documentation from code r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | Move the rest of the features to generated docs | Aleksey Kladov | 2020-05-31 | 1 | -77/+84 |
| | | |||||
* | | Add semantic highlight to QUESTION token | Roland Ruckerbauer | 2020-05-29 | 1 | -0/+1 |
|/ | | | | Made it an operator with controlFlow modifier. | ||||
* | Add self keyword semantic token type | Laurențiu Nicola | 2020-05-25 | 1 | -0/+1 |
| | |||||
* | Handle more cases in `highlight_name_by_syntax` | Matthew Jasper | 2020-05-24 | 1 | -11/+19 |
| | |||||
* | Highlight `true` and `false` as literals | Matthew Jasper | 2020-05-24 | 1 | -0/+1 |
| | |||||
* | Color attribute functions | George Fraser | 2020-05-19 | 1 | -1/+3 |
| | |||||
* | Color `for` as a regular keyword when it's part of impl _ for _ | George Fraser | 2020-05-10 | 1 | -1/+8 |
| | |||||
* | Color `in` as a control keyword | George Fraser | 2020-05-10 | 1 | -1/+2 |
| | |||||
* | Highlight the name in macro declarations | Matthew Jasper | 2020-05-10 | 1 | -0/+13 |
| | |||||
* | Highlight mutable statics as mutable | Matthew Jasper | 2020-05-10 | 1 | -1/+7 |
| | |||||
* | Introduce new semantic highlight token for format specifier | Leander Tentrup | 2020-04-28 | 1 | -1/+1 |
| | |||||
* | Rename StructField -> Field | Aleksey Kladov | 2020-04-25 | 1 | -1/+1 |
| | |||||
* | Convert code to text-size | Aleksey Kladov | 2020-04-25 | 1 | -6/+6 |
| | |||||
*-. | Merge #3998 #4006 | bors[bot] | 2020-04-24 | 1 | -56/+168 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3998: Make add_function generate functions in other modules via qualified path r=matklad a=TimoFreiberg Additional feature for #3639 - [x] Add tests for paths with more segments - [x] Make generating the function in another file work - [x] Add `pub` or `pub(crate)` to the generated function if it's generated in a different module - [x] Make the assist jump to the edited file - [x] Enable file support in the `check_assist` helper 4006: Syntax highlighting for format strings r=matklad a=ltentrup I have an implementation for syntax highlighting for format string modifiers `{}`. The first commit refactors the changes in #3826 into a separate struct. The second commit implements the highlighting: first we check in a macro call whether the macro is a format macro from `std`. In this case, we remember the format string node. If we encounter this node during syntax highlighting, we check for the format modifiers `{}` using regular expressions. There are a few places which I am not quite sure: - Is the way I extract the macro names correct? - Is the `HighlightTag::Attribute` suitable for highlighting the `{}`? Let me know what you think, any feedback is welcome! Co-authored-by: Timo Freiberg <[email protected]> Co-authored-by: Leander Tentrup <[email protected]> Co-authored-by: Leander Tentrup <[email protected]> | ||||
| | * | Adapt format specifier highlighting to support escaped squences and unicode ↵ | Leander Tentrup | 2020-04-22 | 1 | -22/+41 |
| | | | | | | | | | | | | identifiers | ||||
| | * | Apply suggestions from code review | Leander Tentrup | 2020-04-22 | 1 | -4/+3 |
| | | | | | | | | | | | | Co-Authored-By: bjorn3 <[email protected]> | ||||
| | * | Implement syntax highlighting for format strings | Leander Tentrup | 2020-04-20 | 1 | -3/+66 |
| | | | | | | | | | | | | | | | | | | | | | Detailed changes: 1) Implement a lexer for string literals that divides the string in format specifier `{}` including the format specifier modifier. 2) Adapt syntax highlighting to add ranges for the detected sequences. 3) Add a test case for the format string syntax highlighting. | ||||
| | * | Refactor flattening logic for highlighted syntax ranges | Leander Tentrup | 2020-04-18 | 1 | -54/+85 |
| | | | |||||
* | | | Introduce ActiveParameter | Aleksey Kladov | 2020-04-24 | 1 | -5/+3 |
|/ / | |||||
* / | Add semantic tag for unresolved references | Aleksey Kladov | 2020-04-18 | 1 | -14/+15 |
|/ | | | | | | | | | | | This is a quick way to implement unresolved reference diagnostics. For example, adding to VS Code config "editor.tokenColorCustomizationsExperimental": { "unresolvedReference": "#FF0000" }, will highlight all unresolved refs in red. | ||||
* | Fix incorrect order of syntax highlight ranges | Leander Tentrup | 2020-04-17 | 1 | -1/+2 |
| | |||||
* | Merge #3826 | bors[bot] | 2020-04-08 | 1 | -5/+54 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | 3826: Flatten nested highlight ranges during DFS traversal r=matklad a=ltentrup Implements the flattening of nested highlights from #3447. There is a caveat: I needed to add `Clone` to `HighlightedRange` to split highlight ranges ~and the nesting does not appear in the syntax highlighting test (it does appear in the accidental-quadratic test but there it is not checked against a ground-truth)~. I have added a test case for the example mentioned in #3447. Co-authored-by: Leander Tentrup <[email protected]> | ||||
| * | Simplify HTML highlighter and add test case for highlight_injection logic | Leander Tentrup | 2020-04-06 | 1 | -1/+7 |
| | | |||||
| * | Flatten nested highlight ranges during DFS traversal | Leander Tentrup | 2020-04-03 | 1 | -6/+49 |
| | | |||||
* | | Make control token modifier less ambiguous | Aleksey Kladov | 2020-04-06 | 1 | -1/+1 |
|/ | | | | | | | | | In textmate, keyword.control is used for all kinds of things; in fact, the default scope mapping for keyword is keyword.control! So let's add a less ambiguous controlFlow modifier See Microsoft/vscode#94367 | ||||
* | Fix imports | Aleksey Kladov | 2020-03-03 | 1 | -6/+2 |
| | |||||
* | Rename NameDefinition -> Definition | Aleksey Kladov | 2020-03-03 | 1 | -12/+12 |
| | |||||
* | Highlight assist tests | Aleksey Kladov | 2020-03-03 | 1 | -1/+1 |
| | |||||
* | Remove stray dbg | Aleksey Kladov | 2020-03-03 | 1 | -2/+2 |
| | |||||
* | More principled approach for gotodef for field shorhand | Aleksey Kladov | 2020-03-02 | 1 | -13/+17 |
| | | | | | Callers can now decide for themselves if they should prefer field or local definition. By default, it's the local. | ||||
* | Remove debug print | Aleksey Kladov | 2020-02-29 | 1 | -1/+0 |
| | |||||
* | Correctly flag 'lifetime definitions as definitions | Aleksey Kladov | 2020-02-28 | 1 | -2/+7 |
| | |||||
* | Classify name takes const patterns into account | Aleksey Kladov | 2020-02-28 | 1 | -7/+9 |
| | |||||
* | Fix union classification | Aleksey Kladov | 2020-02-28 | 1 | -1/+1 |
| | |||||
* | Cleanup highlighting tags | Aleksey Kladov | 2020-02-28 | 1 | -13/+17 |
| | |||||
* | add more tags | Aleksey Kladov | 2020-02-28 | 1 | -7/+10 |
| | |||||
* | Refactor string literals | Aleksey Kladov | 2020-02-27 | 1 | -2/+4 |
| | |||||
* | Basic injections | Aleksey Kladov | 2020-02-27 | 1 | -4/+55 |
| | |||||
* | Move tests to a new file | Aleksey Kladov | 2020-02-27 | 1 | -134/+2 |
| | |||||
* | More cleanup | Aleksey Kladov | 2020-02-27 | 1 | -114/+108 |
| | |||||
* | Split loop into orthogonal phases | Aleksey Kladov | 2020-02-27 | 1 | -44/+43 |
| | |||||
* | Cleanup | Aleksey Kladov | 2020-02-27 | 1 | -37/+34 |
| | |||||
* | Minor cleanup | Aleksey Kladov | 2020-02-27 | 1 | -15/+18 |
| | |||||
* | Renam module | Aleksey Kladov | 2020-02-27 | 1 | -2/+2 |
| | |||||
* | Move html highlightig to a separate module | Aleksey Kladov | 2020-02-27 | 1 | -97/+3 |
| | |||||
* | Fix html tests | Aleksey Kladov | 2020-02-27 | 1 | -6/+6 |
| | |||||
* | Better highlightign API | Aleksey Kladov | 2020-02-27 | 1 | -47/+60 |
| |