NativeScript / NativeScript/android-dts-generator
Resolve generics properly and don't include unnamed modules
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 96
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
The AppCues SDK demonstrates a great case of conditions to consider to improve the typing generation.
If types are generated the following issues will be seen:
- generics that aren't resolve to proper class name
- unnamed modules nested within other named packages
- some other generic related cases
Contributor guide
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 generating TypeScript declarations from the AppCues SDK linked in the issue and inspect the output for unresolved generics and unnamed modules nested in named packages. Trace the generator paths responsible for these cases and define completion as proper generic class names, exclusion of unnamed modules, and coverage of the other reproduced generic cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100