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

FIX: empty path enpoints leads to Semantic error => clean empty paths #145

Merged
merged 1 commit into from
Jun 3, 2021

Conversation

Vlczech
Copy link
Contributor

@Vlczech Vlczech commented Jun 3, 2021

  • If multiple OAS files are created, paths defined in other scope are empty in current OAS file. If it is an endpoint with path parameter, Semantic error occurs.
  • Example:
Semantic error at paths ./v1/foo/bar/{foo_bar_id}
Declared path parameter foo_bar_id needs to be defined as a path parameter at either the path or operation level

…aths

* If multiple OAS files are created, paths defined in other scope are empty in current OAS file. If it is an endpoint with path parameter, Semantic error occurs.
* Example: Semantic error at paths ./v1/foo/bar/{foo_bar_id}
Declared path parameter foo_bar_id needs to be defined as a path parameter at either the path or operation level
Copy link
Member

@kemingy kemingy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@kemingy kemingy merged commit d34ac5e into 0b01001001:master Jun 3, 2021
@kemingy kemingy linked an issue Jun 3, 2021 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants