Q&A (please complete the following information)

• Method of installation: [npm, dist assets]
• Swagger-UI version: [>=3.25.1]
• Swagger/OpenAPI versi

In the OpenAPI spec, section "Link Object",
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.2.md#linkObject

the "Examples" table following after the text
"The table below provides examples of runtime expressions and examples of their use in a value:"

contains a confusing "note" in the third row, and I think a "note" is missing in the second row.

Proposed changes:

The official API docs are here

https://developers.google.com/maps/documentation/geocoding/start

I wanted to know if it would be possible to add this API's Swagger doc (and that of similar Google APIs like this).

User story.
As a developer, I can change a referenced example file, so that I can see the changes after a request to prism.

Is your feature request related to a problem?
Prism only watches the spec file for changes and even if it changes, it doesn't reload referenced examples. This is useful because spec files can get extremely big so $ref usage is a must to keep it manageable.

Chore summary
Provide some guidance to the custom function writer with regards to errors

Tasks

• Add a section to functions.md

From https://github.com/stoplightio/spectral/pull/1058/files#r408418822

@P0lip What's the effect from throwing from within a function? Does the whole process crash down? Do we get a special kind of result or a console log?

We'd get a console.l

https://swagger.io/docs/specification/serialization/#query

When explode is set to true on a query param, the expected behavior is that an array of parameters of the same name each gets its own query param like ?name=alice&name=bob, however SwagGen generates this as ?name=alice,bob.

Please describe the request object for the request_parameters_factory.create. Can't find it in source code.

Is it possible to validate a response data?

The extension now supports multi-renderers architecture, which means we can have more than one renderer to render the OpenAPI spec. Each renderer may have its own set of configuration options, and so we need to update the docs to reflect these changes.

Currently, we have most of the copy and links for authentication in our custom renderer. Bring these into the specs so that they can be used in other contexts

https://readme.readme.io/reference/authentication

Unclear to me why the auth endpoint is not documented and we only see a little sentence:

The ReadMe API uses basic authentication with the username as your API key and the password is blank.

In Python this would be:

host = 'https://dash.readme.io'
  
data = {'email': 'foo@bar.io', 
        'password': 'adsfdafjkhadskhjf'