tree-sitter-kotlin icon indicating copy to clipboard operation
tree-sitter-kotlin copied to clipboard

Kotlin grammar for Tree-sitter

Results 49 tree-sitter-kotlin issues
Sort by recently updated
recently updated
newest added

The original bug was that a function applied using the infix syntax such as `a eq b`. This would produce a parse error if the operator started with the letter...

scanner

input: ``` val x: Foo.Bar.() -> Unit = {} ``` output parse tree: ``` (source_file (property_declaration (binding_pattern_kind) (variable_declaration (simple_identifier) (user_type (type_identifier) (type_identifier) (ERROR) (type_identifier))) (lambda_literal))) ```

Fixes https://github.com/fwcd/tree-sitter-kotlin/issues/151

grammar

Example test case that fails: ``` ================== Comma in annotation property ================== class EnvironmentSpec { @Option( names = ["--environment", "--env"], arity = "0..1", description = [ "Which environment to use",...

Hello! Any idea when you would be adding support for the newest version of treesitter (0.23)? Thanks for all your hard work on this parser.

Here https://mingodad.github.io/lua-wasm-playground/ there is an easier/cleaner way to write tree-sitter grammars like `Kotlin` (select `Tree-sitter-ebnf-generator-Kotlin` from `Examples` then click `Run` to see a full commented out `grammar.js` from the `EBNF`...

The latest Node.js bindings use prebuildify, but the package published to npm is published without any prebuilds, it should be published with prebuilds, see https://github.com/tree-sitter/workflows/blob/main/.github/workflows/package-npm.yml for how the parsers in...

Configuring environments would be a nice improvement to the deployment workflows, since they show up as progress indicators and links on the repository homepage. See e.g. [this npm example](https://github.com/fwcd/lsp-repl/blob/c1e70f2788775de674d8849b4cb207775dfddf09/.github/workflows/publish.yml) or...

ci-cd