rokucommunity / rokucommunity/brighterscript
how to handle libpkg:/ with autoImportComponentScripts
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
We should give an option for which scheme the auto-imported component scripts use.
We have a few approaches here:
- always use
pkg:/ - always use
libpkg:/ - use
libpkg:/if we have at least 1 instance oflibpkg:/anywhere in the project, or some variation of this.
Should probably give the user a few different options?
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 locating the autoImportComponentScripts implementation and examining how it currently chooses between pkg:/ and libpkg:/. Review the listed scheme-selection approaches and existing project usage, then define and implement a clear configurable behavior with coverage for the selected options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100