swagger-api / swagger-api/swagger-ui
DISCUSS: Should we rewrite this project into TypeScript？
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
More and more projects from the community have migrated to TS. such as react-router and redux.
If you'd like to see a swagger-ui project with typescript, I'd love to move all code here into TS.
We can do a minimal migration first: just add the type without changing the runtime semantics.
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
No files, tests, or entry points are named; start by reviewing the project structure and current JavaScript build setup. Define the migration scope and success criteria before changing code, including whether the minimal migration preserves runtime behavior and adds types throughout the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- build-system, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100