Validator does not resolve ref's with / in key names about oas-kit HOT 6 CLOSED

I've implemented a similar JSON ref parser in python in this project & code. This may help as a reference example.

from oas-kit.

Seems that the when resolving external references here and here it falls back to resolveInternal() which in tern calls jptr.jptr(root, pointer) here.

Cursory search shows jptr implements ~1 parsing properly.

from oas-kit.

In trying to develop a simple test case for this I also found that the components/schemas/<name> validation is too specific, not allowing / characters:

e.g.

openapi: 3.0.0
info:
    title: Example API
    description: Tests ~1 resolving in ref
    version: 0.0.1

servers:
  - url: 'https://localhost:8080/'
    description: Example
paths:
    "/":
        get:
          responses:
            '200':
              description: Example
              content:
                application/json:
                  schema:
                    type: array
                    items:
                      $ref: '#/components/schemas/Example~1Respnse'

components:
    schemas:
        "Example/Response":
            required:
                - Id
            properties:
              Id:
                type: string
                format: uuid
                example: "d2014f64-ffdf-487b-8d12-67a20976aca6"

Resulting in:

Gathering...
#/components/schemas/Example/Response
component name invalid
examples/pathrefs.yml
  Example API 0.0.1
  https://localhost:8080/

Failures:
examples/pathrefs.yml

from oas-kit.

/ is not valid in a component name.

"All the fixed fields declared above are objects that MUST use keys that match the regular expression: ^[a-zA-Z0-9\.\-_]+$"

Sorry for being terse, on my phone.

from oas-kit.

Re: the first point, did you install v2.7.0 from npm, or update a git clone? If the latter, you may need to npm i to bring in the latest version of jgexml / jptr.

from oas-kit.

@MikeRalphson you're spot on here. Turns out it's not the pointer but the external resolution. I'll open a separate issue w/ details and a partial solution.

from oas-kit.