Support Mincer 0.5.x and new option to pass in own Mincer object #11
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
clarkdave
added a commit
that referenced
this pull request
Dec 18, 2013
Support Mincer 0.5.x and new option to pass in own Mincer object
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.
With this ConnectMincer now supports Mincer 0.5.x, but loses the ability to support 0.4.x.
Pay close attention when you upgrade as you will also be moving to a new Mincer version which may (but shouldn't) have some unexpected results.
You can now also pass in your own Mincer object, if you want to require a different version of Mincer than the one which is bundled. This version must be >= 0.5.x though.