swagger-api / swagger-api/swagger-codegen

Model Mapping of 400/500 error code

Open
#2,602 7 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Client: Java Enhancement: Feature help wanted Issue: Workaround available
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

I have generated java client for my rest api. I have specified models for error responses 400 and 500 also but always i get error back as APIException and whole json is copied as string in ApiException.

Has anybody faces this issue and happen to resolve it?

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 generated Java client's ApiException handling and the declared 400/500 error models, then reproduce the response mapping with a minimal REST API response. Done means the generated client exposes the specified error model instead of copying the full JSON into ApiException.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.