Skip to content
This repository has been archived by the owner on Feb 3, 2018. It is now read-only.

Allow (?) custom schemes on vanity imports #208

Open
sdboyer opened this issue Apr 4, 2017 · 2 comments
Open

Allow (?) custom schemes on vanity imports #208

sdboyer opened this issue Apr 4, 2017 · 2 comments

Comments

@sdboyer
Copy link
Owner

sdboyer commented Apr 4, 2017

It should be possible to specify a custom scheme (http vs. https, possibly more) when relying on a vanity import source. But the deduction system poops out earlier than it should. Specifically, this check is wrong because it's actually failing on the wrong kind of error - we should be getting this error back, but we never actually make it that far.

@sdboyer
Copy link
Owner Author

sdboyer commented Apr 4, 2017

At least...it seems like specifying such a scheme should be possible. Maybe it shouldn't be. That's something we may want to figure out here, too 😄

@fabulous-gopher
Copy link

This issue was moved to golang/dep#414

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants