Fix load path order, preferring cwd #13
Closed
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
|
Any news on that? |
|
I'll take a look this weekend. |
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.
Proposed fix for issue #12
This commit no longer pushes to the
Graph.loadPathsarray, but instead creates a local loadPaths array with the cwd concatenated withGraph.loadPaths–this should ensure that the loadPaths from one module don't bleed over into another. There's still one part of the code that might be depending onGraph.loadPathsat #L74, however–but it's not clear why that's needed and tests appear to pass regardless.I also had to change the fixtures directories up a little bit to add a new test case for this issue.