openapi-specification

Hi there! I see that an issue #2884 deeplinking was integrated to 3.x however if I have a hyperlink with a hash to the operationID nothing happens on click. If I reload the page the UI scrolls to the open panel as expected. Is there something I am missing here? My url looks as follows and I am using the 3.0 dist repo installed via npm.

Again when clicked the URL address is updated but nothing h

This is used, for example, when inspecting the result type of SerializerMethodField.

While not technically in violation of the OpenAPI specification, including a query parameter in a path should be flagged as an error in Spectral:

A path has specific meaning in HTTP as a part of a URL that comes after the host name and before the query string or fragment. A "path item" key must be only a path, it cannot have a query string or a fragment.

For example, the following when def

Instead of relying on our own types, we should consider using an NPM module such as this.

This will reduce the likelihood of mistakes, such as with #345 and #346, as well as help us stay up to date.

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

I would like to be able to inspect the Looker API response data to better understand the type of error I have got when performing an action. Knowing that information I can then go on to perform a different set of actions after the error.

For example the create_user can have a variety of [responses](https://docs.looker.com/reference/api-and-integration/api-reference/v3.1/user#response_messages