allow using latest version of money gem for development #719
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.
Hello!
I am opening this PR to be able to unblock #698.
The goal is to be able to always develop against the latest version of
money
Gem (or a branch if you wish so) instead of a published version (because that can still take a few days!)I also learned about
eval_gemfile
today and adjusted the rails gemspecs to avoid duplication inspired but what @sunny suggested here #716 (comment) 😳PS: I removed the Guard* gems, what is that? the
Guardfile
rings a bell, but I don't remember ever using that, andguard-rspec
hasn't been updated in FOREVER so I just 🧹PS2: I haven't forgotten about the mongo tests... 😇