swagger-api / swagger-api/swagger-ui
Global getComponent injection
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Our handaround of getComponent is getting a bit out of hand these days...
A better solution would be to hijack getComponent to inject itself into the props of any component fetched through it, so it's available everywhere.
Care would need to be taken to make sure the getComponent function reference doesn't change over time, to avoid needless renders across the UI.
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 locating the getComponent implementation and the path used to fetch components. Determine how injected props should behave and how to preserve a stable getComponent reference; done means fetched components receive it without causing needless UI renders. No specific files or tests are named, so trace the existing component flow before defining the implementation and test scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100