Skip to content

Bundle doesn't correctly resolve components before processing paths #2750

@jjongsma

Description

@jjongsma

Describe the bug
I have a multi-file spec, where paths and operations are included as $refs. Whenever I bundle, any operation $ref to #components/schemas/SchemaName gives a bundler error of "Can't resolve $ref", even though that schema is defined in the root components.schema object. If I --force the bundling, linting the output verifies that all refs are in fact valid, so it's just the bundler that is confused.

Expected behavior
References to components.schemas should be properly resolved.

I'd also like to dynamically populate components.schemas with a NamedSchemas decorator, so ideally the entire components tree would be processed before paths in order to resolve refs properly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions