Interpolations (`{{valid js code}}`) and directive attributes
(`<element :directive="valid js code"`) can also be typescript code,
hence we can inject typescript instead of javascript here and still
be ok with highlights (bar some syntax differences between ts and js)
* feat(nim): added nim parser and queries
* correct scanner.cc to scanner.c
Co-authored-by: Christian Clason <c.clason@uni-graz.at>
* fix(nim): corrected capture for @function.macro
* feat(nim highlights): added @field capture for discriminator field in
object variant
* bumped parser version, adapted highlights.scm and condensed
injections.scm
* improved nim_format_string highlights.scm
* bump nim parser version again
* removed overlap between queries for generalized strings in
injections.scm
* improved formattin] in nim_format_string/injections.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* corrected asm parser name in injections.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* improved formatting in highlights.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* removed @error capture from highlights.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* improved wording in comment in highlights.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* removed priority from (dot_expression left: @none) capture, since it's
at the end of the file anyways
* removed comments listing unused captures
* reverted @error capture in nim_format_string/highlights.scm back to
@none
* condensed string alternatives in injections.scm
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* condensed string alternatives in injections.scm (second part)
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
* added comment to explain reasoning behind priority use
* swapped order of @punctuation.delimiter and @operator to get rid of
superfluous comment
* moved macro and template keywords to @preproc capture
* removed priorities in highlights.scm and shifted @parameter capture
behind @type capture
* improved formatting in locals.scm
* added queries for missing cases of @definition.namespace capture in
locals.scm
* removed some trailing whitespace
* added @namespace queries for highlights.scm
* bumped parser version again
* removed superfluous @type capture
* removed `@type`s `has-ancestor` and removed `(_ (_ ...` structures,
but added priorities
* added missing @constant capture to some queries in highlights.scm
* fixed priority numbers so they work when injecting nim (in markdown)
* added @none captures back to injection targets
* added (assembly_statement) injection query
* added indent queries
* removed indents.scm again
* added some missing queries for dot_generic_call, concept_declaration and
pragma_statement
---------
Co-authored-by: Christian Clason <c.clason@uni-graz.at>
Co-authored-by: ObserverOfTime <chronobserver@disroot.org>
As discussed in PR#5421, capturing `@error` is inconsistent, requiring
deep nesting (or priority) in order to correctly have red backgrounds to
it.
Some queries has this capture, some don't. For consistency purposes,
removing all of them is more preferable.
For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)`
to your custom queries.
* make sure affine_group has priority, so parens and comma will not be miscolored; added `annotation` as @attribute
* `then` is not used as conditional, so moved to keywords
* finalize function highlight added
* differentiate between constant and variable variable identifiers
This change does two main things:
1. Indicate that `(for_expression)`'s introduce a `@scope` (this
is the scope for the enumerators to be used within the loop).
2. Indicate that the `(identifiers)` within the `(enumerators)` are
`@definition.var`s.
---
For the following example snippet:
```scala
val fruits = List("apple", "banana", "avocado", "papaya")
val countsToFruits = fruits.groupBy(fruit => fruit.count(_ == 'a'))
for ((count, fruits) <- countsToFruits) {
println(s"with (fruits) 'a' × $count = $fruits")
}
```
The `count` and `fruits` identifiers are new definitions introduced by
the `for` expressions scope.
- Consider functions with only one value on the rhs as variables
- Applied composition: `(f . g) <param>` -> `@function.call`
- View patterns
- `@field` in record update expression
- type_tuple and type_list as variables
- quantifier for `exp_apply (<rhs>)+ (variable)`
- type_tuple and type_list as variables
- Treat signatures with only one value on the rhs as variables
(except for `IO a`) -> Fixes#5505.
- Remove redundant anchors from signature function queries.
- Move signature function queries to give them higher priority
- Scoped function types
- Add signature query to function with parameters query
