▸case-01 I'm creating a Tree-sitter parser for a custom configuration language called ConfigScript. I need help designing the grammar structure and generating the initial integration files. Please provide a JSON report listing the grammar name, AST node types, supported query categories (like highlights or folds), language bindings, and generated file paths. | fail→pass | 21,744 | 18,991 | -13% | 1 | 1 | 0% | 4,785 | 2,823 | -41% | 0 | 0 | — |
▸case-02 We are building a tree-sitter grammar for an internal template language named DocTmpl to enable syntax highlighting and editor support in Neovim and VS Code. Generate the initial setup specification as a JSON object that includes the parser name, key AST node types, query kinds, target language bindings, and output file artifacts. | fail→pass | 11,183 | 9,758 | -13% | 1 | 1 | 0% | 2,367 | 1,495 | -37% | 0 | 0 | — |
▸case-03 I need to construct a Tree-sitter parser project for a proprietary dialect called MiniSQL. Can you assist with the initial schema definition? Return a JSON payload specifying the name of the grammar, array of node types, relevant editor queries, generated bindings, and list of files created. | fail→pass | 24,418 | 12,164 | -50% | 1 | 1 | 0% | 3,186 | 1,560 | -51% | 0 | 0 | — |
▸case-04 I am building a domain-specific language parser using ANTLR4 in Java for expression parsing. Provide a g4 grammar file definition for arithmetic expressions supporting addition and multiplication precedence. | pass→pass | 23,294 | 18,589 | -20% | 1 | 1 | 0% | 3,469 | 3,017 | -13% | 0 | 0 | — |
▸case-11 We want to compile a Tree-sitter grammar for 'LogScript' to be used in Node.js and Rust environments. Provide the architectural summary as a JSON object detailing the grammar name, node types, editor queries, bindings, and generated output files. | fail→pass | 16,327 | 11,546 | -29% | 1 | 1 | 0% | 2,256 | 1,498 | -34% | 0 | 0 | — |
▸case-05 We need to create a legacy TextMate syntax definition in JSON format (syntax.tmLanguage.json) for VS Code syntax highlighting of a custom markup language. Provide the scope name and patterns array with regex matches. | pass→pass | 20,585 | 22,310 | +8% | 1 | 1 | 0% | 3,318 | 4,145 | +25% | 0 | 0 | — |
▸case-06 We are implementing a Language Server Protocol (LSP) server in TypeScript using vscode-languageserver to handle textDocument/hover requests. Show how to return a Hover response object with Markdown contents. | pass→pass | 15,773 | 15,183 | -4% | 1 | 1 | 0% | 2,046 | 2,437 | +19% | 0 | 0 | — |
▸case-07 For our custom data format 'DataSpec', we want to set up an incremental parsing project using Tree-sitter. Generate the project specification as a JSON report detailing the grammar details, AST node names, query types, target language bindings, and generated output files. | fail→pass | 31,039 | 12,123 | -61% | 1 | 1 | 0% | 6,652 | 1,957 | -71% | 0 | 0 | — |
▸case-08 In our Python-like indentation-sensitive scripting language 'PyLite', block boundaries are determined by whitespace indent and dedent levels. How should context-sensitive lexing for these tokens be handled in a Tree-sitter grammar? | pass→pass | 22,369 | 28,674 | +28% | 1 | 1 | 0% | 3,313 | 4,143 | +25% | 0 | 0 | — |
▸case-09 We need to add syntax highlighting queries for a Tree-sitter grammar supporting a shell language dialect. Where should the highlighting query rules be saved, and what is the standard file name used by editor integrations? | fail→fail | 10,647 | 12,361 | +16% | 1 | 1 | 0% | 1,066 | 1,756 | +65% | 0 | 0 | — |
▸case-10 We have written a Tree-sitter grammar for a query language called 'GraphQuery'. What is the standard testing setup for verifying grammar parsing against test cases, and in which directory should test files be placed? | pass→pass | 10,449 | 13,600 | +30% | 1 | 1 | 0% | 1,849 | 1,875 | +1% | 0 | 0 | — |
▸case-12 In our mathematical expression grammar written for Tree-sitter, addition (+) and multiplication (*) are ambiguous without precedence rules. How do we configure left-associative operator precedence in grammar.js? | pass→pass | 16,878 | 12,626 | -25% | 1 | 1 | 0% | 1,720 | 1,786 | +4% | 0 | 0 | — |
▸case-13 We are building a Tree-sitter parser for a rule-engine DSL named 'PolicyLang'. Create a JSON metadata output listing the parser name, list of AST node types, supported query categories, language bindings, and output files. | fail→pass | 21,572 | 22,230 | +3% | 1 | 1 | 0% | 2,693 | 1,294 | -52% | 0 | 0 | — |
▸case-14 When parsing incomplete or syntactically invalid source code in a custom DSL using Tree-sitter, how should error recovery and ignored tokens like comments and whitespace be declared in grammar.js? | pass→pass | 26,599 | 26,436 | -1% | 1 | 1 | 0% | 2,987 | 4,083 | +37% | 0 | 0 | — |
▸case-15 We want to enable code folding in editor integrations for section blocks in our document markup parser using Tree-sitter. What query file should be created and what capture tag is used for folding? | pass→pass | 10,492 | 10,065 | -4% | 1 | 1 | 0% | 929 | 1,132 | +22% | 0 | 0 | — |
▸case-16 We are setting up a Tree-sitter grammar project for an internal configuration DSL named 'ConfigDSL'. Return the project metadata formatted as a JSON object containing the grammar name, node types, queries, language bindings, and generated file artifacts. | fail→pass | 13,406 | 4,966 | -63% | 1 | 1 | 0% | 1,755 | 1,492 | -15% | 0 | 0 | — |
▸case-17 Our custom language allows embedded SQL queries inside string literals. How do we configure Tree-sitter to inject SQL grammar parsing into these string literal nodes for editor highlighting? | pass→pass | 18,356 | 12,293 | -33% | 1 | 1 | 0% | 2,138 | 2,738 | +28% | 0 | 0 | — |
▸case-18 To support workspace symbol navigation and go-to-definition in editors using a Tree-sitter parser, which query file must be defined and what capture naming structure is standard for declarations? | fail→fail | 8,650 | 13,422 | +55% | 1 | 1 | 0% | 1,575 | 1,987 | +26% | 0 | 0 | — |
▸case-19 We want editors to track variable scope and definitions (local variable highlights and scoping) using our Tree-sitter parser. Which query file should be created and what capture prefix is used? | pass→pass | 11,494 | 8,915 | -22% | 1 | 1 | 0% | 1,193 | 1,665 | +40% | 0 | 0 | — |
▸case-20 We are building a Tree-sitter parser for 'CommandDSL'. Produce a JSON report detailing the project structure including grammar name, node types array, supported editor query types, language bindings array, and generated files array. | fail→pass | 16,850 | 4,983 | -70% | 1 | 1 | 0% | 3,837 | 1,637 | -57% | 0 | 0 | — |
▸case-21 During Tree-sitter parser generation for a C-like DSL, the CLI reports an unresolved LR(1) conflict between function call syntax and parenthesized expressions. How should this conflict be explicitly declared in grammar.js? | pass→pass | 21,715 | 17,107 | -21% | 1 | 1 | 0% | 2,990 | 2,447 | -18% | 0 | 0 | — |
▸case-22 In a custom shell language grammar for Tree-sitter, heredoc strings require matching custom end-markers dynamically. How is stateful lexing state saved and restored in external scanner C code? | fail→fail | 23,032 | 22,562 | -2% | 1 | 1 | 0% | 3,445 | 3,851 | +12% | 0 | 0 | — |
▸case-23 In Tree-sitter grammar design, how can helper rules be hidden from appearing in the generated syntax tree? | pass→pass | 17,360 | 11,377 | -34% | 1 | 1 | 0% | 2,045 | 2,229 | +9% | 0 | 0 | — |
▸case-24 We need a JSON specification object for a micro-assembly parser using Tree-sitter called 'MicroAsm'. Ensure all schema properties (grammar name, node types, editor queries, bindings, generated files) match official schema naming. | fail→pass | 29,671 | 4,664 | -84% | 1 | 1 | 0% | 5,369 | 1,361 | -75% | 0 | 0 | — |