OpenAPITools / OpenAPITools/openapi-generator

[BUG] Path validation failed for /applications/{path:.+}:

Open
#13,923 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
  • [Yes ] Have you provided a full/minimal spec to reproduce the issue?
  • [Yes ] Have you validated the input using an OpenAPI validator (example)?
  • [Yes ] Have you tested with the latest master to confirm the issue still exists?
  • [Yes ] Have you searched for related issues/PRs?
  • [Yes ] What's the actual output vs expected output?
  • [Yes ] [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

I currently have a path as

/applications/{path:.+}:

Which works till version before 6.2.0 , when I upgrade to 6.2.0 then I get following error:

[ERROR] 
org.openapitools.codegen.SpecValidationException: There were issues with the specification. The option can be disabled via validateSpec (Maven/Gradle) or --skip-validate-spec (CLI).
 | Error count: 1, Warning count: 2
Errors: 
	-paths.'/applications/{path:.+}'. Declared path parameter path:.+ needs to be defined as a path parameter in path or operation level
Warnings: 
	-paths.'/applications/{path:.+}'. Declared path parameter path:.+ needs to be defined as a path parameter in path or operation level
openapi-generator version

6.2.0

OpenAPI declaration file content or url
Generation Details
mvn clean install

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 OpenAPI path /applications/{path:.+} and the SpecValidationException produced during mvn clean install; compare validation behavior before and after version 6.2.0. Done means this declaration validates without treating path:.+ as an undefined path parameter, while preserving normal path-parameter validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, openapi
Domain
api
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.