You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've never seen it working, so I can't really describe what I expect to happen, other than I expect it to work without an error, and I expect to be able to download the PDF file sent in the response when testing the mock server in a tool such as Stoplight or Redocly.
Possible Workaround/Solution
Just providing the URL of the example PDF document as a string instead of using the externalValue property removes the error from the Prism CLI output, however when attempting to actually download the file, it is corrupted or fails to open. But it's arguabaly a better experience than an outright error, albeit still not a solution.
Context
I am trying to document a PDF content type response in an openapi spec, and mock the response by running
prism mock path/to/file
.Current Behavior
When I attempt the process described above, I get the error:
Request terminated with error: Error: Cannot find serializer for application/pdf
.An example of the spec (that follows the latest syntax and best practice) that causes the problem:
Expected Behavior
I've never seen it working, so I can't really describe what I expect to happen, other than I expect it to work without an error, and I expect to be able to download the PDF file sent in the response when testing the mock server in a tool such as Stoplight or Redocly.
Possible Workaround/Solution
Just providing the URL of the example PDF document as a string instead of using the
externalValue
property removes the error from the Prism CLI output, however when attempting to actually download the file, it is corrupted or fails to open. But it's arguabaly a better experience than an outright error, albeit still not a solution.The text was updated successfully, but these errors were encountered: