Turns out a file path with a space breaks the execution of scuri command line

Just getting into creating spec files for my projects so not sure what I am missing here.
When I generated a spec for a file it added import { autoSpy } from 'autoSpy'; but cant find a package for autoSpy.

This might not be an issue since SCuri and SCuri-code assume user is working in an Angular workspace context. Still, for the record:

Seems that when scuri-code gets used out if angular workspace context (for example in the scuri repo for the example app components) we can not seem to get the folder correct :

Notice the CWD and the --name argument respectively finish and start with the same folder (scuri)

c:\Users\gparl\projects\scuri>c:\Users\gparl\AppData\Roaming\Code\User\globalStorage\gparlakov.scuri-code\deps\node_modules\.bin\schematics 
..\..\AppData\Roaming\Code\User\globalStorage\gparlakov.scuri-code\deps\node_modules\scuri\src\collection.json:spec 
--name scuri/example/angular-5-app/src/main.ts  --debug false --debug false
            The file scuri/example/angular-5-app/src/main.ts is missing or empty.
 (ERROR LINE)
            Params: name: scuri/example/angular-5-app/src/main.ts update: false
Nothing to be done.

Be able to run SCuri Create AutoSpy in the context of an open file /or an angular app/ and generate an auto-spy.ts next to it

Scuri 1.2.0 and later now ships the /dist folder while 1.1.0 and before ships the /src folder.

Add logic to use the correct path when doing commands

It show output which makes for an obnoxious user experience (for users that use terminal or entirely hide the panel below)

After installing plugin Create spec command was failing with schematics not found error. I followed the path and saw that ~/.config/Code/User/globalStorage/gparlakov.scuri-code/deps was empty. After closing and reopening Code folder has stuff and command was working.

Sorry, I didn't take the time to test if it replicates.

Code version info:

Version: 1.62.3
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:00:36.721Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.4.0-90-generic

There is an error message when npm test is run - looks like webpack/ts/something else misses the test files and does not compile them...

With the main command Scuri Generate we pass in undefined as a last parameter - which still works but does not look good

SCuri is in the process of rolling out the feature to use custom templates via terminal parameters or config. That will be available for SCuri-code users out of the box.

A nice user experience would be to have to command from VS Code SCuri: Add custom template

That will use something like the https://gist.github.com/gparlakov/f299011829e229c9d37cf0cb38506d97 and then let the users start from a working template.

Example - Scuri create (overwrite) seems to fail when changes are in the git staging (before committing them) but the error remains hidden in the SCuri log

When user is in the context of the .spec.ts file support the Scuri Update and Scuri Create (overwrite) commands.