-
Notifications
You must be signed in to change notification settings - Fork 351
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
feat: STOP-243 - create prism instance with full spec #2501
Conversation
@@ -640,7 +640,7 @@ describe('body params validation', () => { | |||
}); | |||
|
|||
describe('and size bigger than 10MB', () => { | |||
test('returns 422', async () => { | |||
test('returns 413', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was checking a 413, so I updated the title to match.
the rest of the changes in this file are formatting changes
}, | ||
}; | ||
const result = decycle( | ||
await new $RefParser().dereference(specFilePathOrObject, { resolve: { http: httpResolverOpts } }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@daniel-white we are going to leave this here and then add a check for unresolved external references in our usage of this code and error at that point.
…m code that assumes the request came in from a socket
58f75fe
to
81bfbe8
Compare
81bfbe8
to
794b321
Compare
Co-authored-by: Ed Vinyard <[email protected]>
Addresses: STOP-243
Summary
Introduces
createAndCallPrismInstanceWithSpec
that allows you to pass in a prism config, prism request and an oas spec path or document and get a prism response or an error string back.Checklist