Skip to content

fix(ts-lsp): resolve JSX calls from top-level arrow components - #2579

Open
lorenzozanee wants to merge 1 commit into
DeusData:mainfrom
lorenzozanee:fix/tsx-arrow-jsx-calls
Open

lorenzozanee wants to merge 1 commit into
DeusData:mainfrom
lorenzozanee:fix/tsx-arrow-jsx-calls

Conversation

@lorenzozanee

Copy link
Copy Markdown
Contributor

What does this PR do?

Top-level const arrow components currently lose semantic CALLS edges to components rendered in JSX. This routes direct and export-wrapped arrow initializers through the existing TypeScript LSP body processor, preserving exact source-site resolution.

Validation: TMPDIR=/tmp scripts/test.sh --suites ts_lsp (311 passed) and TMPDIR=/tmp scripts/test.sh --suites extraction (434 passed). scripts/lint.sh did not complete because clang-tidy, cppcheck, and clang-format are unavailable.

AI disclosure: Prepared with OpenAI Codex on behalf of @lorenzozanee.

Fixes #2559

Checklist

  • Every commit is signed off (git commit -s) — required, CI rejects
    unsigned commits (DCO, see CONTRIBUTING.md)
  • Tests pass locally (make -f Makefile.cbm test)
  • Lint passes (make -f Makefile.cbm lint-ci)
  • New behavior is covered by a test (reproduce-first for bug fixes)

Signed-off-by: lorenzozanee <wyz0707@proton.me>
@github-actions

Copy link
Copy Markdown

Thanks for opening this — it has been seen, and it is queued.

This note is automated, but it is not a brush-off: it exists so you know where your PR stands instead of having to guess from silence.

Current review status: working through a backlog. 0.9.1-rc.1 is out, so the release freeze that held reviews is over — but it left a large queue of open pull requests behind it, and we are reading through them oldest-first. The background is in discussion #1144.

What that means for this PR, concretely:

  • It will not be closed for inactivity. No stale bot touches pull requests here.
  • It may still sit a while before a human reads it. That is on us, not on you.
  • Older PRs are read first, so a recent one is not being skipped — it is behind a queue.

Things that will genuinely speed it up whenever review does happen:

  • Keep it rebased on main — the tree is moving quickly right now, and a conflicting branch cannot be reviewed as the diff you intended.
  • Get CI green, or say which failures you believe are pre-existing.
  • Keep the change to one claim. Bundled features and refactors get split before they get merged, which costs you a round trip.
  • Every commit needs a sign-off (git commit -s) — CI enforces DCO.

If this fixes a bug, a reproduction we can run is worth more than a description of the symptom.

Thanks for contributing, and sorry in advance for the wait.

This branch has not been deployed

No deployments
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.

Regression since 0.10.0: JSX render edges dropped from arrow-function components (const X = () => <Child/>)

1 participant