[BUGFIX] Use correct POST body for submitting the glossary #172
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
NarkNiro
force-pushed
the
feature/post-body
branch
from
39f17ed
to
3c4837a
Compare
NarkNiro
approved these changes
Apr 28, 2023
There was a problem hiding this comment.
Hello @koehnlein,
Thanks for your pull request, I have cross-checked it and adjusted some styling.
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 have glossary with ~4900 entries. When trying to submit it to DeepL, I received an exception:
I could solve it, by moving the body content from the Request to the options.
For any reason, guzzle's
PrepareBodyMiddlewarewas not able to calculate the correct content length for your way.