Proper escaping and quoting for special characters #52
Conversation
This file contains hidden or 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
maoe
pushed a commit
that referenced
this pull request
Mar 5, 2018
v1.3.0 * Relax upper version bound for base ([#51](#51)) * Implement proper escaping and quoting for special characters ([#51](#51), [#52](#52)) * Introduce the Measurement type and accompanying functions * Fix a bug in the HTTP writer where the precision parameter is ignored when constructing requests * Some minor doctest fixes
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.
After I merged #51, I found some discrepancies between what the official doc says and what we do in the library, namely:
So this PR changes those types accordingly. This contains breaking changes.