Closed plastikfan closed 3 years ago
WindowsTerminalSettingsPath may not be avilable in the built module. Also, make sure that any reference to is subject to Test-Path, so that there are no errors if TerminlaBuddy is installed but WindowsTerminal isn't.
branch: fix-settings-path
See: https://powershell.anovelidea.org/powershell/how-i-implement-module-variables/
Use module scope (ie script scope)
WindowsTerminalSettingsPath may not be avilable in the built module. Also, make sure that any reference to is subject to Test-Path, so that there are no errors if TerminlaBuddy is installed but WindowsTerminal isn't.
branch: fix-settings-path
See: https://powershell.anovelidea.org/powershell/how-i-implement-module-variables/