Skip to content

impact file:line: a field initializer's line names the method declared in it - #1790

Merged
swapnilpaliwal-sd merged 1 commit into
0.1.9from
loop/ja-is1752
Sep 29, 2026
Merged

swapnilpaliwal-sd merged 1 commit into
0.1.9from
loop/ja-is1752

Conversation

@swapnilpaliwal-sd

Copy link
Copy Markdown
Contributor
  • impact <file>:<line> on a class field whose initializer declares a method (static cfg = make({ run() {…} })) now answers that method instead of the field plus 22 [alongside] rows; <static-init>/<instance-init> and the initializer's own arrow still count as the field's.
  • A const answered by file:line gets the same (at file:line) header as every other file:line answer; the wrapped-handler checks now expect it.
  • New checks: an instance-field initializer (the same shape), plus 3 controls (a static field whose initializer only calls, an instance field, an arrow in an initializer) that must stay the field.
  • Checked: tests/run.py --lang javascript 236/236 (was 202/204). This changes the query layer only, so graph edges are unchanged. The full all-language run was still going when this PR was opened.

Closes #1752

… declared in it

A field initializer that declares its own method (static cfg = make({ run() {} }),
api = client({ fetch() {} })) now answers that method; the node that runs the
initializers (<static-init>/<instance-init>) and the initializer's own arrow stay
part of the field. A const/field answered by file:line carries the same
'(at file:line)' header as every other file:line answer.

Closes #1752

Co-authored-by: axiomcode-bot[bot] <334110751+axiomcode-bot[bot]@users.noreply.github.com>
Co-Authored-By: Claude <noreply@anthropic.com>
@swapnilpaliwal-sd
swapnilpaliwal-sd merged commit a19a51e into 0.1.9 Sep 29, 2026
12 checks passed
@swapnilpaliwal-sd
swapnilpaliwal-sd deleted the loop/ja-is1752 branch September 29, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant