chore: normalize PowerShell files to UTF-8 BOM + CRLF - #15
Merged
Merged
Conversation
…ributes Align SPSTrust with the shared SPS* encoding policy (SPSUpdate / SPSWeather / SPSUserSync / SPSFbaSync): - Add a root .gitattributes that stores .ps1/.psm1/.psd1 as UTF-8 with BOM and checks them out with CRLF, while keeping YAML/Markdown/JSON as LF with no BOM. - Re-encode every PowerShell file under src/ and tests/ to UTF-8 with BOM + CRLF. Windows PowerShell 5.1 (used on SharePoint servers) reads BOM-less files as ANSI (the system code page), which corrupts any non-ASCII character; a UTF-8 BOM makes the encoding explicit and safe. Encoding-only change: file contents are otherwise unchanged.
Pester Test Results88 tests 88 ✅ 2s ⏱️ Results for commit 0e2ff56. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Align SPSTrust with the shared SPS* encoding policy (SPSUpdate / SPSWeather / SPSUserSync / SPSFbaSync): PowerShell files (
.ps1/.psm1/.psd1) stored as UTF-8 with BOM and checked out with CRLF; YAML/Markdown/JSON kept as LF, no BOM.Changes
.gitattributesencoding the policy above.src/andtests/to UTF-8 with BOM + CRLF.Why
Windows PowerShell 5.1 (used on SharePoint servers) reads BOM-less files as ANSI (the system code page), which corrupts any non-ASCII character. A UTF-8 BOM makes the encoding explicit and safe.
Notes
Encoding-only change: file contents are otherwise unchanged. No version bump, no tag — this ships with the next functional release.
Validation