• Add new ConnectorError types:
  • UnprocessableContent: The request could not be handled because, while the request was well-formed, it was not semantically correct. For example, a value for a custom scalar type was provided, but with an incorrect type
  • BadGateway: The request could not be handled because an upstream service was unavailable or returned an unexpected response, e.g., a connection to a database server failed
• Generate TypeScript declaration maps for better "go to definition" tooling