Aravind K P
Aravind K P
Thanks for this amazing library. I wanted to raise a question/concern regarding the behaviour of `JSONToYAML` function. ### Example 1 Say I have the following JSON ``` var s =...
### Version Information Server Version: v2.8.0 CLI Version (for CLI related issue): v2.8.0 ### Environment OSS ### What is the expected behaviour? When using `hasura metadata clear` or Clicking "Reset"...
### Version Information Server Version: [v2.10.1](https://github.com/hasura/graphql-engine/releases/tag/v2.10.1) CLI Version (for CLI related issue): [v2.10.1](https://github.com/hasura/graphql-engine/releases/tag/v2.10.1) ### Environment OSS/Cloud/EE ### What is the current behaviour? Let's take a look at the following scenario...
Currently, most of the errors returned from CLI are raw responses from the server, this is not ideal. For example, if we are applying metadata, the error returned will be...
## The Change The commit e2669d38 adds a single line in lib/runner/nested-request.js:133: customParallelIterations: false This option is passed when creating a new runner for nested requests (requests invoked via pm.execution.runRequest())....