rokucommunity / rokucommunity/brighterscript
Support named type imports
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 208
- Forks
- 68
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 39
Description
import type { ActualInterfaceName as AliasName } from "../somewhere.bs"
import type { ActualInterfaceName } from "../somewhere.bs"
we should support importing named (and renamed) types for import statements. This would allow pulling interfaces (and enums, consts) over from files that would potentially cause runtime collisions if the files were actually imported together. Build the symbol table using the types specified, but do not inject imports.
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 tracing how import statements are parsed and how the symbol table is built for imported types. Support named and aliased type imports for interfaces, enums, and consts, while ensuring the corresponding imports are not injected; verify behavior with the project's existing import or compiler tests.
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
- 45/100