Added ability to pass raw data to post, get, put and delete so we can encode data as we want #315
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
…o we can manually encode JSON with custom flags
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.
Hello,
As mentioned in this #300, we cannot send utf8 encoded emojis in
HTML-PartandText-Part.This MR handle that, by not using the
jsonoption of Guzzle if the content is not an array. This is not a BC Break because array are still working as it is.I allow passing data as body or json, so it feel more relevant when calling methods with array|json vs string.
Also, i added the possibility to change content-type in each calls, still having application/json by default.