Actually set ENVied.config #18
Merged
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
|
Nice catch! I'm not sure when @eval will have time to merge this into the mainline gme, but I've forked a copy of this repo for my own use that I've been trying to keep up to date. Thanks for the fix! |
|
Thanks! |
|
👍 |
|
@eval, any chance of a release with this fix? By-hand installs are annoying, and I'm starting a new thing which doesn't have a private gem repo (yet), and I'd hate to have to fire one up for this one bugfixed gem. |
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.
I was surprised to discover that calling
ENVied.confignever actually returned a config object, even after I'd calledENVied.require. Turns out it was never being set. Now it is, with tests to make sure.