rokucommunity / rokucommunity/brighterscript
go to definition should not wait for first validate
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
It seems that sometimes go-to-definition still waits for the first validate. But once we've finished parsing, it should not be waiting since the AST is fully parsed and available.
(I had this in my notes for a while, I'm not sure if this is still an issue, but it needs to be investigated).
bsc version: v0
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
Start by reproducing go-to-definition while the first validation is pending, then compare its behavior after parsing has completed. Trace the validation and AST readiness entry points to determine why the request still waits. Done means go-to-definition responds without waiting once parsing has finished, with a regression test covering that timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100