swagger-api / swagger-api/swagger-parser

Fully resolve external referenced schemas

Open
#938 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

This ticket is about allowing (possibly using a flag to activate behaviour) to resolve all definitions in external files not directly referenced but which themselves reference a directly referenced definition (e.g. a Dog having alIOf = Pet, where Pet is directly referenced and Dog is not.
This is a follow up on #927 after #930 was implemented and #995 after #1004 was implemented

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

Review the related work in #927, #930, #995, and #1004 to understand the existing external-schema resolution behavior. Trace how directly referenced definitions are resolved, then determine how transitive definitions such as Dog referring to Pet should be handled and whether a flag is required. Done means all applicable definitions in external files are resolved, with the requested behavior covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.