Updating custom modules via vscode creates new files under .universal

Updating custom modules via vscode creates new files under .universal

avatar
Product: PowerShell Universal
Version: 5.0.16


I’ve got a strange problem and I don’t know if its on purpose or if I made any mistake but if I change any own created module via vscode it shows up on git commit as a new file under .universal/NewFileNameHere and the original module isn`t updated.

I’m using the version 4.2.4 of the plugin.

For example I’ve created a new module via the dashboard


e5692c8c1fc03e8bd255173c390fb21d31629141
added some functions via the vscode plugin and reloaded the configuration via the vscode plugin


c18b8732c35fe31760e767bc5ec1a8db413882a6
and this shows up on my git commit


695c5af5f746f9b9b02e52fb832b3ff7000b2db2
This didn’t occured on the 4.4.1 version

695c5af5f746f9b9b02e52fb832b3ff7000b2db2.png

c18b8732c35fe31760e767bc5ec1a8db413882a6.png

e5692c8c1fc03e8bd255173c390fb21d31629141.png

All Comments (1)

avatar

This is likely a bug. Feel free to open an issue in the tracker.

Adam Driscoll
PowerShell Expert and Developer at Devolutions