Overview

• Fix int32 and int64 format validation

Overview

• consistent mock results, fixes #264

Overview

• #261 Fix query string validation

Overview

New: Added --skip-verify option to prism mock, prism serve and prism validate commands to disable ssl cert verification.

Fix: Support example property when dynamically mocking a JSON Schema
Fix: Improve mock 400 response when request is invalid
Fix: Date format mocking
Fix: Mocking property pattern on JSON Schema
Fix: Time format mocking
Fix: Loading environment variables from a url

Overview

• Fix: Better error message when mocking fails,link to Prism FAQ when mocking fails
• Fix: Can't set $$.env variables when reffing a scenario script
• Fix: Can't override global security schemes

Overview

• Fix downloading oas, prism instances and scenario files

Overview

• Consume new export api
• Use jwt tokens for auth
• Bug fixes

Overview

• Better errors when loading oas, scenarios and prism instances fail
• Update prism help command output

Overview

• Fixes AWS Authentication

Overview

• prism validate now validates requests
• add to javascript runtime SL.prism.generateToken(...)

Overview

• fix downloading exporting versions from stoplight when conducting scenarios and serving prism instances
• fix resolving complicated circular ref chains

Overview

• update mock scripts
• update JSON Schema Faker to latest
• fix prism instances matching on methods

Issues

• fixes https://github.com/stoplightio/desktop/issues/247

Overview

• set status code on options so that prism doesn't try to forward request when mocking
• fix local refs for prism instances
• fixes automatic status code assertions
• pass oas specs between scenario refs properly

Overview

• Bug fixes

Issues

• fixes https://github.com/stoplightio/prism/issues/127
• fixes https://github.com/stoplightio/prism/issues/144

Overview

• update prism mock command

  • Mock server now respects security schemes and will return a 401/403 if defined in your oas
  • Request body and headers are validated.
  • If request validation fails, then respond with a 400 response defined in your spec.
  • Add CORs
  • Validate response body and headers

Overview

• Prism Instances modify the location header by setting the host to the prism host
• Add "type" property to validation message, type is the type of validation error
• Don't dereference specs that are already dereferenced

Overview

• improved error handling and reporting from the JavaScript runtime

Overview

• Authenticate private OAS files for transitive refs

Overview

• Load multiple spec files for Scenario Collections and Prism Instances
• Fix panic when loading multiple specs

Overview

• Don't make calls to the exporter for local references