Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semantic error at paths #1617

Closed
gitforpushpak opened this issue Jan 3, 2018 · 4 comments · Fixed by #1620
Closed

Semantic error at paths #1617

gitforpushpak opened this issue Jan 3, 2018 · 4 comments · Fixed by #1620

Comments

@gitforpushpak
Copy link

gitforpushpak commented Jan 3, 2018

Hi,

I am seeing below error when I import my json into the https://app.swaggerhub.com

swagger: '2.0'

Semantic error at paths./{baseSiteId}/{lang}/{areaCode}/users/{userId}/customergroups
Declared path parameter "baseSiteId" needs to be defined as a path parameter at either the path or operation level

my controller has the above mapping.

/{baseSiteId}/{lang}/{areaCode}/users/{userId}/customergroups
How can I fix this issue ?

thanks.

@shockey
Copy link
Contributor

shockey commented Jan 3, 2018

Hi @gitforpushpak!

This is a known bug (#1614) that was introduced by our new validation system last week.

I expect to have this patched within the next day or two, and have a fix released this Friday. SwaggerHub will need to pick the changes up though, you'd need to ask them when they have a release scheduled that will include it.

@gitforpushpak
Copy link
Author

@shockey thanks for the reply. Once you have the patch ready, what should I do ? How it will resolve my error? Can you please explain me?

@shockey
Copy link
Contributor

shockey commented Jan 5, 2018

@gitforpushpak, if you're using SwaggerHub you'll need to wait until the SwaggerHub team updates their service to use the latest version of Swagger-Editor - there's no way for you as a user to swap out the version used within SwaggerHub.

The fix I'm about to merge into our master branch changes the data going into the path item validator, so that $ref'd parameters are correctly taken into account.

(cc: @ponelat)

@shockey
Copy link
Contributor

shockey commented Jan 5, 2018

I closed this as the issue is resolved on our end, but feel free to reply if you have any lingering questions @gitforpushpak!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants