Cannot bundle `$ref` like `./errors.yaml#/400_unexpected`

[pete-woods]

When attempting to bundle my spec, I've run into the following issue. Referencing a raw file works, but referencing an object from within a file does not.

It looks like #418 fixed the document loading for this kind of reference, but bundling seems like it wasn't fixed at the same time.

e.g.

  responses:
    "200":
      $ref: ../components/responses/Unspecified200.yaml # works
    "400":
      $ref: '../components/responses/4xxClientErrors.yaml#/400_unexpected_request_body' # does not work
    "403":
      $ref: '../components/responses/4xxClientErrors.yaml#/403_permission_denied' # does not work

I've created some tests for this in #499.

[pete-woods]

Digging in a little, at least some of the issue seems to be converting the ref to a jsonpath.

It first gets converted to $.403_permission_denied, then sent to your jsonpath library. When tokenizing the path, it comes out with the 403 and _permission_denied as separate tokens (INT and STRING respectively). The parsing code then understandably rejects it.

i.e. the issue is identifiers starting with a number.

[daveshanley]

this is related to #473

However I can tune the JSONPath conversion tool to handle numbers. it already supports the same format with non numbers.

[pete-woods]

this is related to #473

However I can tune the JSONPath conversion tool to handle numbers. it already supports the same format with non numbers.

I do feel like the correct fix would be with the jsonpath tokenizer to not be tricked into treating the prefix as a separate token.