This could be the same issue I am experiencing.
I have re-imported a spec into editor.swagger.io and receive the same
error.
For me this appears to relate to having defined a path parameter in the
parameters section and using $ref. Defining query parameters in this manner
works fine. I am convinced it worked last month:
/{someparam}/somepath:
get:
...
parameters:
- $ref: '#/parameters/someparam'
...
...
parameters:
someparam:
in: path
name: someparam
required: true
type: string
Regards
On Wednesday, 3 January 2018 08:46:28 UTC, Pushpak Ubale wrote:
>
> Hi
>
>
> I am seeing lots of error after importing my api json.
>
> Sample Error: Semantic error at
> paths./{baseSiteId}/{lang}/{areaCode}/vouchers/{code} Declared path
> parameter "baseSiteId" needs to be defined as a path parameter at either
> the path or operation level Jump to line 3788
>
>
> How should I fix this? Is this due to version issue?
>
>
> I integrated swagger with my project to generate the /api-docs
> then i saved the json
> and imported into the swaggerhub
>
>
>
> Thanks in advance
>
--
You received this message because you are subscribed to the Google Groups
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
