rokucommunity / rokucommunity/brighterscript
Document an npm tag that all bsc plugins should use to improve discoverability
Open
Nobody has claimed this yet.
good first issue
help wanted
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
It might be worth picking some type of npm tag like brighterscript-plugin or bsc-plugin and publically documenting that on the brighterscript readme, to help with discoverability of plugins
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 repository README and review its existing plugin-related content. Confirm the npm tag convention to document, then add the chosen tag and usage guidance to the README; done means plugin authors can find and apply the convention from the documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100