Coverage generated as 0% and paramters is 'null' in a case if parameter is a reference to component parameters block

[adzest]

I'm submitting a ...

• bug report

What is the current behavior?

Coverage report score 0% and a parameter is 'null' If the openapi3 spec contains parameter as ref to component/parameters block:
`paths:
/pets:
get:
summary: List all pets
operationId: listPets
tags:
- pets
parameters:
- $ref: '#/components/parameters/pets_limit'

...

components:
parameters:
pets_limit:
name: limit
in: query
description: How many items to return at one time (max 100)
required: false
schema:
type: integer
format: int32
example: 1`

If the current behavior is a bug, please provide steps to reproduce, broken swagger specification, and swagger-coverage-output:

• openapi3 spec:
  `openapi: "3.0.0"
  info:
  version: 1.0.0
  title: Swagger Petstore
  license:
  name: MIT
  servers:
  • url: http://petstore.swagger.io/v1
    paths:
    /pets:
    get:
    summary: List all pets
    operationId: listPets
    tags:
    - pets
    parameters:
    - $ref: '#/components/parameters/pets_limit'
    responses:
    '200':
    description: A paged array of pets
    headers:
    x-next:
    description: A link to the next page of responses
    schema:
    type: string
    content:
    application/json:
    schema:
    $ref: "#/components/schemas/Pets"
    default:
    description: unexpected error
    content:
    application/json:
    schema:
    $ref: "#/components/schemas/Error"
    post:
    summary: Create a pet
    operationId: createPets
    tags:
    - pets
    responses:
    '201':
    description: Null response
    default:
    description: unexpected error
    content:
    application/json:
    schema:
    $ref: "#/components/schemas/Error"
    /pets/{petId}:
    get:
    summary: Info for a specific pet
    operationId: showPetById
    tags:
    - pets
    parameters:
    - name: petId
    in: path
    required: true
    description: The id of the pet to retrieve
    schema:
    type: string
    responses:
    '200':
    description: Expected response to a valid request
    content:
    application/json:
    schema:
    $ref: "#/components/schemas/Pet"
    default:
    description: unexpected error
    content:
    application/json:
    schema:
    $ref: "#/components/schemas/Error"
    components:
    parameters:
    pets_limit:
    name: limit
    in: query
    description: How many items to return at one time (max 100)
    required: false
    schema:
    type: integer
    format: int32
    example: 1
    schemas:
    Pet:
    type: object
    required:
    - id
    - name
    properties:
    id:
    type: integer
    format: int64
    name:
    type: string
    tag:
    type: string
    Pets:
    type: array
    items:
    $ref: "#/components/schemas/Pet"
    Error:
    type: object
    required:
    - code
    - message
    properties:
    code:
    type: integer
    format: int32
    message:
    type: string`
• use maven dep:
  <dependency> <groupId>com.github.viclovsky</groupId> <artifactId>swagger-coverage-rest-assured</artifactId> <version>1.4.1</version> </dependency>
• run GetPets.shouldSee200 test
• coverage output contains 'limit' field
• serve the report with
  ./1.4.1/bin/swagger-coverage-commandline

What is the expected behavior?

Coverage has a 'limit' parameter.

What is the motivation/use case for changing the behavior?

Expected behavior for base open spec functionality.

Other information

tag_name: 1.4.1

[kk2491]

@adzest Were you able to find a work around for this bug?

Thank you

[ruiTLF]

@viclovsky I'm also facing this issue . Will this be fixed ?
Thanks !

[adzest]

Hi, no, we patch the yml or json source file before usage.

…

On Fri, 14 Jan 2022 at 04:50, KK ***@***.***> wrote: @adzest <https://github.com/adzest> Were you able to find a work around for this issue? Thank you — Reply to this email directly, view it on GitHub <#83 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACG5PRORB7JVYNF5W6TS54TUV6FPBANCNFSM44VJ4DTQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Best regard, *Oleksii Isakov* Cell +38 098 302 0018 | Skype: alex.isakov3 LinkedIn <http://www.linkedin.com/profile/view?id=196966332&trk=hb_tab_pro_top> | Facebook <https://www.facebook.com/aleksej.isakov.14> | VK <http://vk.com/isakov.aleksey>