microsoft / microsoft/multilspy
Cross-file reference not working in typescript
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 610
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
I am running the multilspy typescript client on this repo: https://github.com/rchl/test-tsx.
from multilspy import SyncLanguageServer
from multilspy.multilspy_config import MultilspyConfig
from multilspy.multilspy_logger import MultilspyLogger
config = MultilspyConfig.from_dict({"code_language": "typescript"}) # Also supports "python", "rust", "csharp", "typescript", "javascript", "go", "dart", "ruby"
logger = MultilspyLogger()
lsp = SyncLanguageServer.create(config, logger, "/workspaces/test-tsx/")
with lsp.start_server():
result = lsp.request_references(
"feature.tsx", # Filename of location where request is being made
9, # line number of symbol for which request is being made
18 # column number of symbol for which request is being made
)
print(result)
It is able to detect the references from the same file, but it is not able to detect the reference of Feature Component in app.tsx. Am i missing something here.
More information: https://github.com/typescript-language-server/typescript-language-server/issues/271
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the request_references call from the issue against the linked test-tsx repository, checking feature.tsx and the Feature reference in app.tsx. Compare the behavior with the linked typescript-language-server issue 271 and trace the TypeScript language-server client path. Done means cross-file references are returned for this example, with regression coverage if the relevant test location is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100