rokucommunity / rokucommunity/brighterscript
Validate auto-discovered manifests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
In the absence of bsconfig.json files, the language server will explore all the folders for manifest files.
This is unsafe as the extension may be active while editing non-Roku projects which may also include manifest files.
The discovery mechanism should validate that the manifests "look like" Roku manifests (e.g. "ini" files with maybe a title= entry)
See #1518 where a TODO is added
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 with the manifest-discovery TODO added in #1518 and trace the language server's auto-discovery mechanism. Add or update tests for distinguishing Roku-like manifests from unrelated manifest files; done means non-Roku projects are not activated while valid Roku manifests remain discoverable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100