swagger-api / swagger-api/swagger-ui
Runtime configuration for features
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
I would like to enable / disable given features that can be configured via the Swagger-UI configuration at runtime.
This would enable users to get to know several features.
Example if one does not know that there is a filter how he will never know because it is hidden behind a flag.
I want to highlight that with this, features, that cannot be enabled on default, because this would result in a breaking change, at least could be promoted via a given runtime configuration panel.
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 reviewing Swagger UI’s existing configuration and feature-flag behavior, then inspect the linked runtime-panel example. The issue names no files or tests; completion would require an agreed scope for runtime feature controls and verification that users can enable or disable supported features through Swagger UI.
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