Home>Blog>
Stoplight v1.1.5 Release

Stoplight v1.1.5 Release

Platform, Studio, and Prism

Brought to you by Stoplight

The #1 API Design Platform

Try Stoplight

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Platform v1.1.5

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Features

  • Added β€œView in Docs” button to explorer read panel
  • Docs endpoint pages now display the method and path
  • Navigating between docs pages will now scroll you to the top of the page
  • Docs page table of contents is displayed as a popover on smaller screens

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Fixes

  • Images in docs now point directly to the original repository, rather than to jsdeliver
  • Parameters with long names no longer overflow into their type
  • Correctly shows how your docs will look on mobile screens in the docs preview

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Studio v1.1.4

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Features

  • Support operation parameter references
  • Support running spectral rules on JSON schema files: #122

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Fixes

  • Opening a project can sometimes get stuck on the β€œprocessing” screen indefinitely
  • Project failing to open results in removed project folder
  • Multiple line breaks in markdown cause strange issues: #68
  • Request/response examples display an error in the read view: #80
  • Right click context menu not working in file tree for non git projects
  • Expanding editor window with diagnostics panel causes error in UI: #94

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Prism v3.1.1

πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— πŸ”— Fixes

  • Prism is now giving precedence to application/json instead of using it as a β€œfallback” serializer, fixing some conditions where it wouldn’t get triggered correctly: #599
  • Prism is now taking in consideration the required properties for combined schemas (oneOf, allOf): #575
  • Prism will never have enough information to return a 403 status code; all these occurrences have been now replaced with a 401status code which is more appropriate: #624
  • Prism is now negotiating the error response dynamically based on the validation result (security or schema validation) instead of always returning a static order of responses: #591
  • Prism is now selecting proper serializer when Accept header contains content type which is missing in spec: #589
  • HEAD requests no longer fail with 406 Not Acceptable: #575
Read how world’s leading API first companies are solving API Design Management at Scale.