-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat(sync): functionality to allow revese sync from module to includehelper #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| Import-Module $testhelpermodulepath -Force | ||
| } | ||
|
|
||
| function Assert-AreEqualFiles { |
Check warning
Code scanning / PSScriptAnalyzer
The cmdlet 'Assert-AreEqualFiles' uses a plural noun. A singular noun should be used instead. Warning
| # NestedModules = @() | ||
|
|
||
| # Functions to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no functions to export. | ||
| FunctionsToExport = '*' |
Check warning
Code scanning / PSScriptAnalyzer
Do not use wildcard or $null in this field. Explicitly specify a list for FunctionsToExport. Warning
| FunctionsToExport = '*' | ||
|
|
||
| # Cmdlets to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no cmdlets to export. | ||
| CmdletsToExport = '*' |
Check warning
Code scanning / PSScriptAnalyzer
Do not use wildcard or $null in this field. Explicitly specify a list for CmdletsToExport. Warning
| VariablesToExport = '*' | ||
|
|
||
| # Aliases to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no aliases to export. | ||
| AliasesToExport = '*' |
Check warning
Code scanning / PSScriptAnalyzer
Do not use wildcard or $null in this field. Explicitly specify a list for AliasesToExport. Warning
| @@ -0,0 +1,26 @@ | |||
| Write-Information -Message ("Loading {0} ..." -f ($PSCommandPath | Split-Path -LeafBase)) -InformationAction continue | |||
Check warning
Code scanning / PSScriptAnalyzer
Cmdlet 'Write-Information' may be used incorrectly. Please check that all mandatory parameters are supplied. Warning
| @@ -0,0 +1,52 @@ | |||
| function Remove-TailSpacesAndLines { | |||
Check warning
Code scanning / PSScriptAnalyzer
Function 'Remove-TailSpacesAndLines' has verb that could change system state. Therefore, the function has to support 'ShouldProcess'. Warning
| @@ -0,0 +1,52 @@ | |||
| function Remove-TailSpacesAndLines { | |||
Check warning
Code scanning / PSScriptAnalyzer
The cmdlet 'Remove-TailSpacesAndLines' uses a plural noun. A singular noun should be used instead. Warning
| [Parameter(Mandatory,Position = 0)][ValidateSet([ValidFolderNames])][string]$FolderName | ||
| ) | ||
|
|
||
| return $FolderName |
Check notice
Code scanning / PSScriptAnalyzer
The cmdlet 'Get-Folder' returns an object of type 'System.String' but this type is not declared in the OutputType attribute. Note
A part of the logic to allow reverse sync there is logic to allow spaces and tailing lines cleanup to avoid false positive on file changes during sync due to spaces and lines.
Eliminate trailing whitespace and empty lines across various files to enhance code cleanliness and maintainability. This update includes a script for removing trailing whitespace specifically from PowerShell files.
Commit messages:
refactor(module): recurse sync
feat(tools): add script to remove trailing whitespace from PowerShell files
style: remove tailing whitespaces from all files
refactor(tools): enhance script to remove trailing whitespace and empty lines
style: remove trailing whitespace from multiple files
style: remove trailing whitespace from multiple scripts
style: remove trailing whitespace and empty lines in multiple files