5cc2cc1b89
bindings: rust: include scanner and highlights queries.
2024-12-12 22:15:54 +01:00
0c2b73e65d
bindings: python: include highlights queries
2024-12-12 22:15:24 +01:00
56e2f4e02b
bindings: go: include scanner.
2024-12-12 22:13:19 +01:00
791ec1b1af
README.md: add install instructions for neovim
2024-12-12 19:52:50 +01:00
c7013c130e
adding highlights
2024-12-12 19:41:14 +01:00
7223d87d9e
adding variable support
2024-12-12 19:22:14 +01:00
8c66bd3605
make string_content optional instead of matching empty values.
2024-12-12 17:23:37 +01:00
4d71a8548b
make no distinction between single quoted and double quoted string tokens.
2024-12-12 17:05:31 +01:00
dabedec847
adding hexadecimal and decimal as a subtoken for integer
2024-12-12 16:55:10 +01:00
d0b54d61aa
Update grammar to correctly produce value token
...
Problem was before that for example the input [0x000KKK] would produce a
hexadecimal and a value token (for the respective parts)
However, the more correct way is to have the whole input identified as a
value token. basicly if the whole input between "=" and a special
"end-of-assignment" token can't be identified as a string,bool,integer
whatever. it should be identified as a value token.
2024-12-12 10:55:11 +01:00
e7a97e884a
value token: "=" can be part of the value.
2024-12-11 16:53:04 +01:00
0512ebe640
test/corpus/values.txt: split tests
2024-12-11 12:01:38 +01:00
c0d7c31981
adding license and readme
2024-12-11 11:53:53 +01:00
527ac2368f
adding more number types
2024-12-11 00:43:34 +01:00
adc9052da5
add integer and boolean values
2024-12-10 22:24:26 +01:00
948e93ffac
Initial Commit
2024-12-10 19:51:21 +01:00
