Skip to content

Examples in the referenced paths are parsed differently than those in non-referenced paths. #2111

@StarKhan6368

Description

@StarKhan6368

Hello,

When using OpenAPI Specification where the operations of an endpoint are being referenced using another file, the examples are parsed as strings rather than objects in the absence of a reference.

schema_diff

As observed in the image above, the only distinction is that the operations under /products are referenced in V1, whereas no such reference exists in V2. When flattened out both V1 and V2 are identical. However, the example value and example type do not match when these specifications are parsed.

Expected Behavior

The examples in both V1 and V2 should be parsed consistently as JSON Object.

Actual Behavior

In V1, where the operations are referenced:

V1 Example Value: {id=1, name=XYZ Product, inventory=100}
V1 Example Value Type: class java.util.LinkedHashMap

In V2, where no reference exists:

V2 Example Value: {"id":"1","name":"XYZ Product","inventory":100}
V2 Example Value Type: class com.fasterxml.jackson.databind.node.ObjectNode

Sample Project

I have created a sample repository demonstrating this issue with the failing tests, which can be accessed here, Thank you for your attention to this matter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions