OpenAPITools / OpenAPITools/openapi-generator

[REQ] Feature Request Description allow @Override to be full name

Open
#20,146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: Feature
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Is your feature request related to a problem? Please describe.

allow Override annotation in generated code to be specified as a full java name like @java.lang.Override in templates as if there is Override model class then the compiler will have an issue distinguishing between the model Override class and @java.lang.Override annotation

Describe the solution you'd like

Either use full names including in the java.lang space so that the classes are clear from which package they are coming as by default it is the same package or to allow config settings to specify full java class names to be used

Describe alternatives you've considered

Additional context

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 by tracing how Java templates handle generated @Override annotations and how template or configuration options determine imported and fully qualified class names. Done means generated Java can use java.lang.Override even when a model named Override exists, with coverage for the naming collision; the issue does not identify specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.