Clarification on operationRef in link object specification

[Alan-Cha]

Could you clarify how the operationRef in the link object specification works?

You provided some examples, showcasing how operationRef and operationId can be utilized and even though I found the operationId example understandable, I thought the operationRef example was confusing.

Here is the operationRef example you provided:

components:
  links:
    UserRepositories:
      # returns array of '#/components/schemas/repository'
      operationRef: '#paths~12.0~1repositories~1{$response.body#/username}'

What does "#paths~12.0~1repositories~1" mean? Is "~12.0~1repositories~1" a directory? And shouldn't the operation have an HTTP verb attached to it?

Thanks!

[ePaul]

I guess the idea is to point to this part in the definition:

paths:
  /2.0/repositories/{username}:

The ~1 is a way of JSON pointer to replace / occurring in a property name (because / is already used as level separator).

I don't know if the {$response.body#/username} here is correct (I didn't read that part of the spec in detail).

And yes, if this is supposed to reference an operation, it needs a /get or similar at the end.

[darrelmiller]

The operationRef examples are missing the operation and I will fix those.

[darrelmiller]

Fixed.