swagger-api/swagger-codegen

[JAVA]need `JsonIgnore` on java fluent setter

Open

#5,099 opened on Mar 17, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Client: JavaGeneral: Suggestionhelp wanted

Description

Also want a configuration to diable java fluent setter. Here is my problem: I have a Schema Object which has a property like settlementNo then the generated class will have two setter

 public ConditionRequest settlementNo(String settlementNo) {
    this.settlementNo = settlementNo;
    return this;
  }
  public void setSettlementNo(String settlementNo) {
    this.settlementNo = settlementNo

then with the default configuration of spring-fox and spring-boot , in the spring-fox-swagger-ui the ConditionRequest would have two property

settlementNo(the right one)

tlementNo(the wrong one)

And if both of the property has a value, tlementNo's will overwrite settlementNo's

Contributor guide

Tech stack
java
Domain
backendapitooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaJackson annotationsSwagger Codegen templates
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
The issue proposes adding @JsonIgnore on Java fluent setter methods to avoid duplicate property entries in swagger ui. The fix likely involves modifying the Java codegen templates (e.g., in modules/swagger codegen/src/main/resources/Java/) to annotate the fluent setter. Additionally, a configuration option to disable fluent setters may need to be added to the CodegenConfig interface and related options. The comments and linked discussions show confusion about the exact solution, so examining the existing template for model setter generation and the CodegenConfig options for Java is recommended.