swagger-api / swagger-api/swagger-parser

Unable to parse nested objects in defination or inline schema

Open
#436 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
867
Forks
560
Avg merge
2d 21h
Merged PRs (30d)
7

Description

The workaround as suggested in forum for using $ref is not applicable as the swagger is hosted publicly.
For reference, https://www.postcodeapi.nu/docs/spec.yaml?v=2

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 the parsing failure with the publicly hosted specification at postcodeapi.nu/docs/spec.yaml?v=2, focusing on its nested objects in definitions or inline schemas. Inspect the parser's handling of those schema structures and confirm that the specification parses successfully without requiring a local $ref workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, openapi, yaml
Domain
api, backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.