OpenAPITools / OpenAPITools/openapi-generator

[BUG][JAVA] Duplicated parameters validation not working using relative path parameters

Open
#13,991 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue: Bug
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Bug Report Checklist
  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

The duplicated parameters validation is not failing when the API spec files use a relative path to the parameter. I attach two API's to reproduce the problem, this API the validation is failing because of the parameters are solved using the same file, and this one reproduces the problem, it's not validating the duplicated parameters.

The validation should fail in the both API samples.

openapi-generator version

6.2.1

Generation Details

Java:

  • RestTemplate
  • WebClient

Java Spring

Steps to reproduce

Executing the generation of this API should fail because of the duplicated parameters.

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 reproducing generation with the attached rest-bundled.zip using the Java RestTemplate and WebClient configurations, then compare its validation with rest-original.zip. Trace how duplicated parameters are resolved through the relative path during generation; done means validation fails for both API samples as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.