Fix module import on case-sensitive file systems#4
Open
Suerlink wants to merge 1 commit into
Open
Conversation
Owner
|
excellent. Will add in the next release, much appreciated @Suerlink |
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
2 participants
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.
This (tiny fix) fixes module import on Linux/macOS where the file system is case-sensitive.
The module loader looked for
PublicandPrivate, but the repository folders are namedpublicandprivate. On Windows this still works, but on Linux PowerShell could not find the folders and exported zero commands.This change keeps the path behavior first, then falls back to resolving module subfolders without case compat.
Verified on Ubuntu with PowerShell 7.6.1:
Test-ModuleManifestsucceedsImport-ModulesucceedsNote: I see this script has an Authenticode signature block, so maintainer will need to re-sign it during release.