Leverage the Module Autoload path and save doing it ourselves. #431
Conversation
This file contains 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
This should be faster too as we won't automatically import all functions to the session. Powershell now knows where to look before declaring they don't exist.
MartiUK
added a commit
that referenced
this pull request
Mar 18, 2015
Leverage the Module Autoload path and save doing it ourselves.
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.
The seems like the intended way to do this. Only possible problem is our path is first in the load preferences. Perhaps someone could hijack a native module by loading one of the same name first I've never tried. I think PS has something to avoid collisions. The standard path has the users home
WindowsPowershell\Moduleshere before the system one so I don't think it's a problem.see
$env:PSModulePath.split(';')for the curious. I guess that loads top down, or left to right in that order? We're either last or first.This should be faster too as we won't automatically import all functions
to the session. Powershell now knows where to look before declaring they
don't exist.