This repository was archived by the owner on Aug 26, 2021. It is now read-only.
Fix goPath trimming in NewPackage func #59
Merged
Conversation
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
Owner
|
Hi, thx for PR. |
Contributor
Author
|
Sure. In my case it was a 2 paths list : And my issue was that I ended up with values like |
Owner
|
Thx, I'll look at it shortly. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi!
I have a list of paths as GOPATH, and I was getting absolute paths for all the
goPackagePathvalues in my generateddeps.nix.So I refactored the gopath trimming used by
currentPackage()into a separate function, and used that inNewPackage()instead of thestrings.TrimPrefixthat was there.