support legacy "encoding" if "valueEncoding" is not provided. #8
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
|
Im ok with this 👍 |
juliangruber
added a commit
that referenced
this pull request
Oct 21, 2015
support legacy "encoding" if "valueEncoding" is not provided.
|
thanks dominic! published as 6.1.0 |
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'd like add support for the legacy encoding default behavior, which I had used in a bunch of modules.
I can see the value of tidying up the api a bit, but i just don't think that making a breaking change for such a little thing (a few lines removed) that doesn't make significant improvements, or at least enable those, just isn't really worthwhile if you have to update a bunch of things.