rokucommunity / rokucommunity/brighterscript
support diagnostics for unknown namespace member.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
given that the namespace part zapp is delcared, and is a known namespace, I would expect a diagnostic if writing code like:
zapp.constants
zapp.unknownMethod()
zapp.validNamespace.unknownMethod()
etc.
and it did not exist, as the only possiblity here is for a namespace entity (class sub-namespace, or function).
This would give those of us using namespaces a bunch of extra diagnostics to check for typos in our code, and it should be pretty accurate.
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, tests, or entry points. Start by locating namespace member resolution and the existing diagnostic path, then verify that unknown members in the listed namespace expressions produce diagnostics without flagging valid namespace entities.
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
- 42/100