Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Remove unneeded code, filename from tests, fix rebasing issues | Paul Daniel Faria | 2020-06-27 | 5 | -8/+61 |
| | |||||
* | Revert ide highlighting changes (addressing on another branch) | Paul Daniel Faria | 2020-06-27 | 5 | -57/+4 |
| | |||||
* | Add HighlightTag::Operator, use it for unsafe deref. Move unsafe validation ↵ | Paul Daniel Faria | 2020-06-27 | 5 | -6/+6 |
| | | | | to its own file | ||||
* | Update injection mechanism and stop injecting through highlight element, ↵ | Paul Daniel Faria | 2020-06-23 | 6 | -187/+187 |
| | | | | switch to more general new highlight tag, generic | ||||
* | Add punctuation highlighting for highlighting punctuation in doctests, fix ↵ | Paul Daniel Faria | 2020-06-23 | 6 | -203/+203 |
| | | | | highlighting in doctests | ||||
* | Add default color and opacity for documentation and injected, respectively, ↵ | Paul Daniel Faria | 2020-06-23 | 6 | -0/+12 |
| | | | | in the html generator | ||||
* | Add support for marking doctest items as distinct from normal code, add ↵ | Paul Daniel Faria | 2020-06-23 | 1 | -22/+22 |
| | | | | default tag to all doctest elements | ||||
* | Fix underflow panic when doctests are at top of file | Paul Daniel Faria | 2020-06-23 | 1 | -1/+4 |
| | |||||
* | Syntax highlighting for documentation comments on macro definitions | Leander Tentrup | 2020-06-19 | 1 | -0/+9 |
| | |||||
* | Merge #4903 | bors[bot] | 2020-06-18 | 1 | -38/+38 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | 4903: Add highlighting support for doc comments r=matklad a=Nashenas88 The language server protocol includes a semantic modifier for documentation. This change exports that modifier for doc comments so users can choose to highlight them differently compared to regular comments. Example: <img width="375" alt="Screen Shot 2020-06-16 at 10 34 14 AM" src="https://user-images.githubusercontent.com/1673130/84788271-f6599580-afbc-11ea-96e5-7a0215da620b.png"> CC @woody77 Co-authored-by: Paul Daniel Faria <[email protected]> | ||||
| * | Remove logic to mark all doctest code as | Paul Daniel Faria | 2020-06-18 | 1 | -13/+13 |
| | | |||||
| * | Ensure all existing doctest code highlights have documentation modifier | Paul Daniel Faria | 2020-06-17 | 1 | -13/+13 |
| | | |||||
| * | Add highlighting support for doc comments | Paul Daniel Faria | 2020-06-17 | 1 | -38/+38 |
| | | |||||
* | | Syntax highlighting for escape sequences in strings | Leander Tentrup | 2020-06-17 | 6 | -1/+11 |
|/ | |||||
* | Inspect markdown code fences to determine whether to apply syntax highlighting | Leander Tentrup | 2020-06-16 | 1 | -1/+5 |
| | |||||
* | Syntactic highlighting of NAME_REF for injections | Leander Tentrup | 2020-06-15 | 6 | -6/+22 |
| | | | | | | This commit adds a function that tries to determine the syntax highlighting class of NAME_REFs based on the usage. It is used for highlighting injections (such as highlighting of doctests) as the semantic logic will most of the time result in unresolved references. It also adds a color to unresolved references in HTML encoding. | ||||
* | Fix syntax highlighting of recursive macros | Leander Tentrup | 2020-06-15 | 1 | -0/+8 |
| | | | | Add syntax highlighting for the BANG (`!`) token if the parent is `MACRO_CALL`. | ||||
* | In field patterns, don't highlight local binding as a field | Aleksey Kladov | 2020-06-10 | 1 | -1/+3 |
| | |||||
* | Better unsafe highlihgting tests | Aleksey Kladov | 2020-06-08 | 6 | -7/+13 |
| | |||||
* | Implement syntax highlighting for doctests | Leander Tentrup | 2020-06-08 | 1 | -0/+70 |
| | |||||
* | Fix bug in lexer for format specifier where the `type` and `width` were not ↵ | Leander Tentrup | 2020-06-07 | 1 | -1/+1 |
| | | | | correctly distinguished | ||||
* | Add highlight support for unsafe fn calls and raw ptr deref | Paul Daniel Faria | 2020-06-02 | 5 | -0/+52 |
| | |||||
* | Test case for format string highlighting of closing curlybrace | Roland Ruckerbauer | 2020-05-30 | 1 | -0/+1 |
| | |||||
* | Add self keyword semantic token type | Laurențiu Nicola | 2020-05-25 | 1 | -4/+4 |
| | |||||
* | Highlight `true` and `false` as literals | Matthew Jasper | 2020-05-24 | 4 | -1/+5 |
| | |||||
* | Color attribute functions | George Fraser | 2020-05-19 | 1 | -1/+1 |
| | |||||
* | Color `for` as a regular keyword when it's part of impl _ for _ | George Fraser | 2020-05-10 | 1 | -0/+10 |
| | |||||
* | Color `in` as a control keyword | George Fraser | 2020-05-10 | 1 | -0/+4 |
| | |||||
* | Highlight the name in macro declarations | Matthew Jasper | 2020-05-10 | 2 | -3/+5 |
| | |||||
* | Highlight mutable statics as mutable | Matthew Jasper | 2020-05-10 | 1 | -1/+4 |
| | |||||
* | Introduce new semantic highlight token for format specifier | Leander Tentrup | 2020-04-28 | 4 | -35/+39 |
| | |||||
* | Merge #3998 #4006 | bors[bot] | 2020-04-24 | 1 | -0/+82 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | -0/+5 |
| | | | | | | | | identifiers | ||||
| * | Implement syntax highlighting for format strings | Leander Tentrup | 2020-04-20 | 1 | -0/+77 |
| | | | | | | | | | | | | | | 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. | ||||
* | | Add semantic tag for unresolved references | Aleksey Kladov | 2020-04-18 | 2 | -6/+6 |
|/ | | | | | | | | | | | 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. | ||||
* | Simplify HTML highlighter and add test case for highlight_injection logic | Leander Tentrup | 2020-04-06 | 2 | -5/+44 |
| | |||||
* | Correctly flag 'lifetime definitions as definitions | Aleksey Kladov | 2020-02-28 | 2 | -30/+29 |
| | |||||
* | Fix highlighting of const patterns | Aleksey Kladov | 2020-02-28 | 1 | -4/+11 |
| | |||||
* | Fix highlighting test | Aleksey Kladov | 2020-02-28 | 2 | -38/+42 |
| | |||||
* | Fix html tests | Aleksey Kladov | 2020-02-27 | 2 | -33/+33 |
| | |||||
* | Refactor primary IDE API | Aleksey Kladov | 2020-02-26 | 1 | -6/+6 |
| | | | | | | | | | | This introduces the new type -- Semantics. Semantics maps SyntaxNodes to various semantic info, such as type, name resolution or macro expansions. To do so, Semantics maintains a HashMap which maps every node it saw to the file from which the node originated. This is enough to get all the necessary hir bits just from syntax. | ||||
* | Add module colors to css | Aleksey Kladov | 2020-02-16 | 2 | -0/+2 |
| | |||||
* | Implement Syntax Highlight inside Macro | Edwin Cheng | 2020-01-20 | 2 | -6/+16 |
| | |||||
* | Drop support for legacy colorization | Aleksey Kladov | 2019-12-31 | 2 | -6/+6 |
| | |||||
* | Fix highlighting for field init shorthand | Aleksey Kladov | 2019-12-20 | 1 | -1/+1 |
| | |||||
* | Improve highlighting test | Aleksey Kladov | 2019-12-20 | 2 | -1/+4 |
| | |||||
* | Fix highlighting token names | Aleksey Kladov | 2019-12-17 | 2 | -2/+2 |
| | |||||
* | fixed rainbow-highlighting test | Omer Ben-Amram | 2019-12-15 | 1 | -0/+2 |
| | |||||
* | removed `type.alias` | Omer Ben-Amram | 2019-12-14 | 1 | -12/+14 |
| | |||||
* | Rename GenericParam -> TypeParam | Aleksey Kladov | 2019-12-07 | 1 | -0/+1 |
| | | | | We don't have LifetimeParam yet, but they are planned! |