Skip to content

Reference resolved against wrong components. #139

Open
@KevinMitchell

Description

@KevinMitchell

I have two APIs, Old and New say. In Old there's a reference to a schema S that generates an error in the RefPointer class when it tries to resolve the reference, even though the API defines this schema.. But in API New there is no such schema. When I add some debug code to RefPointer::resolveRef I see that it's trying to resolve the reference in Old with the schemas from New, which explains why it can't resolve it. So are there two separate environments, one for each API, and somewhere it's just using the wrong one? Before I start tracking down the problem further I just wanted to check how this is supposed to work.

Thanks

Kevin

Metadata

Metadata

Assignees

No one assigned

    Labels

    Still Valid?Issue is need to be reproduced on latest build

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions