I haven't had an opportunity to dig deeply, so I'm only seeing what is the most likely culprit, but the recent commit lukesampson/pshazz@9bda1e3 may have adjusted setting up a fresh install in a way that fails to create the config file if it does not exist (as the path does not exist).
This is the error I'm seeing:
Set-Content : Could not find a part of the path 'C:\Users\user\.config\pshazz\config.json'.
At C:\Users\user\scoop\apps\pshazz\current\lib\config.ps1:24 char:27
+ ConvertTo-Json $cfg | Set-Content $configFile -Encoding ASCII
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (C:\Users\user\.config\pshazz\config.json:String) [Set-Content], DirectoryNotFoundException
+ FullyQualifiedErrorId : GetContentWriterDirectoryNotFoundError,Microsoft.PowerShell.Commands.SetContentCommand
I haven't had an opportunity to dig deeply, so I'm only seeing what is the most likely culprit, but the recent commit lukesampson/pshazz@9bda1e3 may have adjusted setting up a fresh install in a way that fails to create the config file if it does not exist (as the path does not exist).
This is the error I'm seeing:
This error occurs immediately after:
Note that running
pshazz init
does not correct the issue.