Skip to content

Conversation

@HeyItsGilbert
Copy link
Member

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Checklist:

  • My code follows the code style of this project.
  • I have updated the documentation accordingly.
  • I have added this change to the CHANGELOG.md.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

* Introduced `Messages.psd1` for localized messages.
* Updated functions to utilize localized messages for warnings and errors.
* Improved formatting and readability in several functions.
* Ensured consistent use of `[CmdletBinding()]` across all functions.
* Documented the addition of localization support in the Unreleased section.
* Fixed the typo in the variable name from `$helpLoc2ales` to `$helpLocales`.\
* Added search exclusion patterns in `.vscode/settings.json`.
* Reformatted command arguments in `.vscode/tasks.json` for better readability.
* Introduced a new task `Bootstrap` in `.vscode/tasks.json` for initialization.
* Updated `PowerShellBuild` version in `requirements.psd1` to `0.7.2`.
* Enhanced test assertions to provide clearer output and ensure all expected files exist.
* Comment out incorrect output path assignment for GitHub Actions.
* Added debug statements to log the output path and contents of the `TestModule` after build.
* Removed redundant count test for PSD1 and dot-sourced functions with specific file look ups.
* Add LocalizedData to PSM incase of load failure
…and improve parameter formatting

* Updated `[cmdletbinding()]` to `[CmdletBinding()]` for consistency.
* Enhanced readability by aligning parameter assignments in `$newMDParams`.
* Added new words to `cspell.json` for better spell checking.
* Migrate `ScriptAnalyzerSettings.psd1` to `tests` directory and update paths.
* Enhance task definitions in `psakeFile.ps1` for better readability and consistency.
* Add new exclusion rule for `PSUseApprovedVerbs` in the script analysis settings.
…andling and suppress warnings

* Added suppression attributes for unused parameters in `Publish-PSBuildModule` and `Test-PSBuildPester`.
* Enhanced `CmdletBinding` attribute casing for consistency.
* Refined parameter validation logic for better clarity and maintainability.
…ate changelog

* Remove extra item from `New-MarkdownHelp` splat to prevent failure with `$PSBPreference.Docs.Overwrite = $true`
* Clean up failing Script Analyzer settings and relocate the configuration file.
…hance psake file

* Introduced two new launch configurations for debugging PowerShell scripts in VSCode.
* Updated `psakeFile.ps1` to correct property casing and added functionality to control documentation overwrite behavior.
* Enhanced tests to verify the documentation overwrite feature.
* Build tests now run in TempDir
* TestModule moved into fixtures folder.
* Added test for docs
…cation`

* Ensures proper stack management for directory changes in tests.
* Improves cleanup in `AfterAll` by restoring the previous location.
* Introduced `BeforeDiscovery` block to ensure the build script is executed if the project path is not set.
* Added `DotSource.psm1` to facilitate dot-sourcing of public functions.
* Updated `psakeFile.ps1` to dynamically import the PowerShellBuild module and log its version.
* Improved handling of temporary directories and paths for better compatibility with GitHub Actions.
Base automatically changed from i18n to main July 30, 2025 15:00
@HeyItsGilbert HeyItsGilbert deleted the TestDocOverwrite branch August 1, 2025 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants