-
When files are uploaded to SAS (/SASjsExecutor endpoint) we need to make them available to the SAS session. Ideally they will be loaded into SASWORK, but until we find a nice way to handle a running …
-
Currently `sasjs request` does not have an option for capturing the log. We should add it as `--log` or `-l` parameters, similar to [sasjs job execute](https://cli.sasjs.io/job).
-
There are two issues with sasjs doc:
1) UNC paths not supported.
This is actually a doxygen limitation on windows, however to avoid confusion, we should identify such paths (eg by the fact the…
-
With the work we did for streaming apps, the JSON produced by `sasjs build` was updated to enable files to be uploaded to both SAS 9 and Viya
The issue is that this was implemented using file path …
-
The recent merge to check the node version broke the release (fixed [here](https://github.com/sasjs/cli/pull/982)).
```text
➜ git npm install -g @sasjs/cli
npm ERR! code 1
npm ERR! path /usr/l…
-
When an asset is not found, an unhelpful message is displayed
![image](https://user-images.githubusercontent.com/4420615/133820373-4c57ace2-264b-4b6b-b95d-409d5553f511.png)
To reproduce:
1.…
-
We need a consistent display name in the service response - currently it differs between SAS9 and VIYA.
![image](https://user-images.githubusercontent.com/4420615/129682926-ee2d51b0-3473-466d-988c-…
-
`v1.9.2` is released and `sasjs docs` command is supported till `v1.9.1`
-
Currently if a test fails we provide the URL of the test in both the console window and the CSV results file to make it easy for the user to just click the link and re-run the test.
For VIYA we nee…
-
Currently when installing the CLI the following message is presented to the user:
```
➜ ~ npm i -g @sasjs/cli
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@sasjs/ada…