perf: use node.type for O(1) operator detection across Go, Rust, Python, JS/TS analyzers

[github-actions]

🤖 This PR was created by Repo Assist, an automated AI assistant.

Summary

Replace sourceText.substring() calls with operatorNode.type for binary and boolean operator detection in the Go, Rust, Python, and JS/TS (jsLikeAnalyzer) analyzers. Also apply two additional O(1) micro-optimisations in the Go and Rust/JS analyzers.

Why this is faster

In tree-sitter, anonymous tokens (e.g. &&, ||, ??, and, or) have their literal text as their .type property. The Java analyzer already uses .type for the same purpose and has done so correctly since the Java analyzer was introduced. This PR brings the other four analyzers into line.

Previously each visit to a binary_expression / boolean_operator / logical_expression node triggered a string allocation via sourceText.substring(operatorNode.startIndex, operatorNode.endIndex). These nodes are among the most common in typical TypeScript/JavaScript/Go/Rust/Python source files.

Changes

All four analyzers: getBinaryOperator / getBooleanOperator / getOperator

-const text = this.sourceText.substring(operatorNode.startIndex, operatorNode.endIndex);
-if (text === "&&" || text === "||") { return text; }
+const type = operatorNode.type;
+if (type === "&&" || type === "||") { return type; }

Go — isRecoverCall

-const funcNode = node.children.find((child) => child.type === "identifier"); // O(n) scan
+const funcNode = node.childForFieldName("function"); // O(1) field access

Rust & jsLikeAnalyzer — else_clause reason detection

-const hasNestedIf = node.children.some((child) => child.type === "if_expression"); // O(n)
+const hasNestedIf = node.firstNamedChild?.type === "if_expression"; // O(1)

Test Status

npm run compile  ✅  (0 errors)
npm run lint     ✅  (0 warnings)
npm run test:unit  ✅  149 passing, 0 failing

The Java analyzer has been using operatorNode.type throughout — that pattern is already validated by the existing test suite. All 149 unit tests (covering binary operators in Go, Rust, Python, JS, and TS) continue to pass unchanged.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• releaseassets.githubusercontent.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "releaseassets.githubusercontent.com"

See Network Configuration for more information.

Generated by 🌈 Repo Assist, see workflow run. Learn more.

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@d63b34de41bc0dc052096e094c732cf28eafc659

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.15%. Comparing base (d5d49b9) to head (e689616).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #412      +/-   ##
==========================================
- Coverage   78.18%   78.15%   -0.04%     
==========================================
  Files          13       13              
  Lines        4167     4161       -6     
  Branches      470      469       -1     
==========================================
- Hits         3258     3252       -6     
  Misses        906      906              
  Partials        3        3              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR optimizes operator detection in several tree-sitter analyzers by avoiding substring() allocations and using SyntaxNode.type (which is the literal token text for anonymous/keyword tokens), plus a couple of small O(1) AST-access tweaks.

Changes:

• Rust/Python/JS-like/Go: switch binary/boolean operator extraction from sourceText.substring(...) to operatorNode.type.
• Go: switch recover() detection from an O(n) child scan to childForFieldName("function").
• Rust & JS-like: change else-clause “else if” detection to an O(1) check (but this introduces a correctness issue for comments/extras between else and if).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/metricsAnalyzer/languages/rustAnalyzer.ts	Uses operatorNode.type for logical operator detection; updates else-clause reason detection (issue: firstNamedChild can be a comment).
src/metricsAnalyzer/languages/pythonAnalyzer.ts	Uses operatorNode.type for and/or operator detection.
src/metricsAnalyzer/languages/jsLikeAnalyzer.ts	Uses operatorNode.type for `&&/
src/metricsAnalyzer/languages/goAnalyzer.ts	Uses childForFieldName("function") for recover() detection; uses operatorNode.type for `&&/