-
Currently, SASJS only fetches the log after the flow has run. It would be good to add a feature to show the log as the flow is running. It will not only help with debugging but also take away some anx…
-
For debugging client issues it is helpful to immediately understand the version being used. We can add this in the server response.
-
We are getting the following warning when installing the CLI:
```
npm WARN deprecated querystring@0.2.0:
```
![image](https://user-images.githubusercontent.com/4420615/125408836-fd232980-e3c3-11…
-
Some Viya jobs take parameters as input. We need to support these in both `sasjs job execute` and `sasjs flow` commands.
We can follow the [approach](https://cli.sasjs.io/context/) taken in `sasjs…
-
if a target has a missing or invalid url, rather than erroring out, we should simply prompt the user to enter a valid serverUrl
![image](https://user-images.githubusercontent.com/4420615/119882050-…
-
When running sasjs deploy with invalid (eg expired) credentials the response is misleading:
`An error has occurred when building services Root folder has to be present on the server.`
In fact th…
-
Expected behaviour:
`sasjs add cred` will use the defaultTarget
![image](https://user-images.githubusercontent.com/4420615/122066108-1eabe800-cdfb-11eb-9ec8-57d779fcb384.png)
-
When `allowInsecureRequests` is `true` in the sasjsconfig we should ensure that self-signed certificates are supported for the `sasjs job execute` command
-
For example:
```
"indata": [
[{"data": "value"}]
]
```
-
The generated build.sas file (used to create services/jobs/tests using SAS code) does not split the tests into the /tests folder in SAS 9