Skip to content

feat: make astQuery a first-class feature#86

Open
isaacs wants to merge 1 commit into
nodejs:mainfrom
isaacs:isaacs/astquery
Open

feat: make astQuery a first-class feature#86
isaacs wants to merge 1 commit into
nodejs:mainfrom
isaacs:isaacs/astquery

Conversation

@isaacs

@isaacs isaacs commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Note: based on #85, land that first

This is the cleanest way to do certain things that cannot be reached by name alone. However, it's brittle to rely on a feature, even a stable one, which is not documented or tested. So, treat it as a first-class feature.

This is the cleanest way to do certain things that cannot be reached by
name alone. However, it's brittle to rely on a feature, even a stable
one, which is not documented or tested. So, treat it as a first-class
feature.
@isaacs isaacs force-pushed the isaacs/astquery branch from c7417fc to 9c7191a Compare July 1, 2026 14:57
@timfish timfish requested a review from a team July 1, 2026 15:03
Comment thread README.md
When present, `astQuery` chooses the nodes to instrument and
takes precedence over `functionQuery`'s matching fields;
`functionQuery` then only supplies behaviour (`kind`, `index`,
`callbackIndex`, `mutableResult`) and may be omitted (it defaults

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mutableResult is no longer a thing.

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.

3 participants