🩹 [Patch]: Update linter configurations and license year #106
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tignore for VS Code files
…ScriptAnalyzer configuration
…ns and improve documentation formatting
…alysis warnings; modify build scripts to output messages directly
…sesToExport function and adjust synopsis formatting
…eManifestAliasesToExport function for console output
…low console output
…files from duplication checks
…ter compatibility
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request includes several updates to the configuration files and PowerShell scripts to enhance code quality and maintainability. The most important changes include updates to the JSCPD and PSScriptAnalyzer configurations, adjustments to the module requirements in various scripts, and suppression of specific warnings.
Configuration Updates:
.github/linters/.jscpd.json: Added a new configuration file for JSCPD to set the threshold to 0, specify reporters, and ignore certain paths..github/linters/.powershell-psscriptanalyzer.psd1: Updated the PSScriptAnalyzer configuration to enable specific rules and adjust the excluded rules.Module Requirement Adjustments:
scripts/helpers/Build-PSModule.ps1,scripts/helpers/Build/Build-PSModuleBase.ps1,scripts/helpers/Build/Build-PSModuleManifest.ps1,scripts/helpers/Build/Get-PSModuleAliasesToExport.ps1,scripts/helpers/Build/Get-PSModuleCmdletsToExport.ps1,scripts/helpers/Build/Get-PSModuleFunctionsToExport.ps1,scripts/helpers/Build/Get-PSModuleVariablesToExport.ps1,scripts/helpers/Build/Import-PSModule.ps1,scripts/helpers/Build/Resolve-PSModuleDependency.ps1,scripts/helpers/Build/Update-PSModuleManifestAliasesToExport.ps1,scripts/main.ps1: Re-added the#Requires -Modulesdirective for required modules and added suppression forPSAvoidUsingWriteHostwarnings. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]License Update:
LICENSE: Updated the copyright year from 2024 to 2025. (F75789b6L1)Linter Workflow Adjustment:
.github/workflows/Linter.yml: Changed the validation setting fromVALIDATE_JSCPDtoVALIDATE_JSON_PRETTIER.Script Output Adjustments:
tests/tools/1-build.ps1,tests/tools/2-build.ps1: Changed the output fromWrite-Hostto a direct string output. [1] [2]Type of change
Checklist