Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Allow (?) custom schemes on vanity imports #414

Closed
fabulous-gopher opened this issue Apr 21, 2017 · 1 comment
Closed

Allow (?) custom schemes on vanity imports #414

fabulous-gopher opened this issue Apr 21, 2017 · 1 comment

Comments

@fabulous-gopher
Copy link

From @sdboyer on April 4, 2017 1:24

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.

Copied from original issue: sdboyer/gps#208

@fabulous-gopher
Copy link
Author

From @sdboyer on April 4, 2017 1:25

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 😄

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

3 participants