rokucommunity / rokucommunity/brighterscript
Support begin/end bs:disable comments
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
tools like eslint support a general "disable this rule until I enable it myself" concept. We should have something similar in bsc. Like this:
'bs:disable 1001
print varNotThere
print varNotThere
print varNotThere
'bs:enable 1001
print varNotThere
~~~~~~~~ error: 1001 var not defined.
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
No files, tests, or entry points are named in the issue. Start by locating how bsc parses comments and emits diagnostic 1001, then trace how diagnostics can be suppressed and re-enabled; done means repeated 1001 warnings are ignored only between the matching bs:disable and bs:enable comments, while later warnings still appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100