swagger-api / swagger-api/swagger-codegen
[Language Agnostic][Client and Models only] Feature Matrix - Decouple the JSON libraries and Client libraries
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Using Scala as an example. In Scala world, we have:
- at least three pure-scala JSON libraries, circe(for scala-cats), Argonaut(for scalaz) and json4s, and the interop work is not out-of-box.
- at least two HTTP Client libraries, http4s(functional), play!(more java-ize).
If you want to support all of these features, you should write N * M kinds of templates, that is not acceptable.
Besides Scala, I believe other languages may face the same problem, there may be lots of components, each component may have lots of selections, and the components may loose-coupling among.
Suggest a fix/enhancement
Maybe we should find a way to modularize the different components, so that each component can update(the version) and change individually.
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 or tests are identified. Start by mapping how client libraries, JSON libraries, and model templates are currently combined, using the Scala examples in the issue as a reference; the work is done when these components can be selected and versioned independently without requiring N×M templates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100