rokucommunity / rokucommunity/brighterscript
Provide better completions for `m.top`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
In BrightScript, m.top is always defined for components, so we should be able to provide more rich completions when m.top. is typed. We know it's a roku scene graph component, so we should show the RSG completions. However, we also need to be smart about it, anytime the script could be included in source scope, those completions should not be available. The same with some types of anonymous functions. I guess as a first step we could implement it everywhere, and then start narrowing it once we have more visibility into the actual usage of the functions.
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
The issue names no files or tests. Start by locating the completion handling for m.top. and the existing RSG completion definitions, then trace how script scope and anonymous functions are identified. Done means showing RSG completions for component m.top usage while excluding contexts that can be in source scope or unsupported anonymous functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100