| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
These will be introduced as part of the 0.19.0 release. This commit
updates the lockfile as well as the relevant queries to accommodate the
new expression and "in" now being a keyword.
|
| |
|
|
|
|
| |
This keyword is deprecated as of 0.18.1 (released on February 12, 2025)
and is being removed as part of the upcoming 0.19.0 release.
BREAKING CHANGE: replace with `type`.
|
| |
|
|
|
| |
This keyword will be released in 0.18.0 and deprecate the "class"
keyword, which in turn will be removed in 0.19.0.
|
| |
|
|
| |
This keyword is added as part of the upcoming 0.18.0 release.
|
| |
|
|
|
| |
The parser added support for the "inline" keyword in a few places. This
ensures a highlight is present for the keyword.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This ensures that when you add a new call line in the middle of a call
chain, the line is indented like so:
foo
.bar
.new_line_here
.baz
Instead of it being indented like so:
foo
.bar
.new_line_here
.baz
|
| |
|
|
|
|
|
|
|
|
|
| |
Inko allows for syntax such as `some_value.42.to_string`, where `42` is
a method name. Similar to other languages that allow this (e.g. Rust),
these numeric names should be highlighted as numbers instead of
identifiers.
To fix this, the query to highlight call names is adjusted to only
highlight "name" and "constant" nodes as the function group, ensuring
the remaining possible node ("integer") continues to use the same group
as regular numbers.
|
| |
|
