swagger-api / swagger-api/swagger-codegen

[Spring] Improvement - Autoinject ObjectMapper instead of creating ObjectMapper in apiController

Open
#5,413 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

One of the enhancement comments from @cbornet from Issue#5310 is that we should auto-inject the ObjectMapper in apiControllers instead of creating it. [https://github.com/swagger-api/swagger-codegen/issues/5310]

Swagger-codegen version

2.2.3-SNAPSHOT

Command line used for generation

language = 'spring'
inputFile = file('src/main/resources/swagger.json')
configFile = file('src/main/resources/config.json')

Related issues

https://github.com/swagger-api/swagger-codegen/issues/5310

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Spring generator templates that produce apiControllers and inspect how ObjectMapper is currently created. Use related issue #5310 for context; done means generated Spring apiControllers auto-inject ObjectMapper instead of creating it directly.

Written by the indexing model from the issue text.

Assessment

Tech stack
spring
Domain
api, backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.