Problem following references when run outside of the root definition directory about openapi-validator HOT 7 CLOSED

🎉 This issue has been resolved in version 0.10.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from openapi-validator.

Actually, forget that. It was a mistake on my end. I passed the parent object of it within a dynamic transformation. Maybe it should rather throw an error about the document not really being an openapi document. I’ll supply an example later.

from openapi-validator.

When used programmatically, it seems to have issues resolving refs on documents it otherwise validates fine, such as:
SyntaxError: Error resolving $ref pointer "/path/to/cwd/#/components/schemas/ref_thing".

from openapi-validator.

@jammi Interesting... you mean it works fine from the command line but fails if you run in as an imported module within code?

from openapi-validator.

Just would like to confirm the original problem statement with relative paths refs.
(If go with the assumption that expected starting point for relative path is document).

Version: ibm-openapi-validator-0.10.2

Files

subdir/main.yml

openapi: 3.0.0
paths:
  /example:
    get:
      summary: Summary
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                $ref: "./schema.yaml#/components/schemas/SchemaDef"

subdir/schema.yaml

openapi: 3.0.0
paths: {}
components:
  schemas:
    SchemaDef:
      type: object

from openapi-validator.

@dhudlow @apestov I am going to look at this issue this week

from openapi-validator.

Update: I identified the source of this issue. There are some challenges to work out but I hope to have a fix out sometime this coming week

from openapi-validator.