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

Allow body validator to be created where possible #41

Merged
merged 1 commit into from
Mar 19, 2020

Conversation

shenie
Copy link
Contributor

@shenie shenie commented Mar 4, 2020

The body validator was not getting created because the reference schema
does not contain the requestPath which in turn is because the way
external file is split (it moves all path of user to a separate file).

As referencedBodySchema is not needed to create the validator that is
needed I have relaxed the guard statement in handleBodyValidation().

The body validator was not getting created because the reference schema
does not contain the requestPath which in turn is because the way
external file is split (it moves all path of user to a separate file).

As referencedBodySchema is not needed to create the validator that is
needed I have relaxed the guard statement in handleBodyValidation().
@coveralls
Copy link

coveralls commented Mar 4, 2020

Pull Request Test Coverage Report for Build 310

  • 3 of 4 (75.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.2%) to 97.139%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/parsers/open-api3.js 3 4 75.0%
Totals Coverage Status
Change from base Build 308: -0.2%
Covered Lines: 552
Relevant Lines: 557

💛 - Coveralls

@kobik kobik merged commit 2ab48cb into PayU:master Mar 19, 2020
@shenie
Copy link
Contributor Author

shenie commented Mar 19, 2020

Thanks!

Would you be able to cut a release with this soon please?

So I can go PR downstream packages that needs this change for supporting split swagger yaml files.

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

Successfully merging this pull request may close these issues.

None yet

3 participants