fix: handle DELETE response correctly in Mailchimp member removal ❗️ #666
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
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Co-Authored-By: Rami Abdou <[email protected]>
ramiAbdou
approved these changes
Dec 11, 2024
ramiAbdou
changed the title
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.
Fix error when removing Mailchimp members by properly handling DELETE response without attempting to parse JSON.
The DELETE request to remove a member from Mailchimp succeeds, but the code was throwing an error when trying to parse the response as JSON. This PR fixes the issue by checking the response status without attempting to parse the response body.
Changes made:
response.json()call since DELETE responses don't have JSON bodiesLink to Devin run: https://app.devin.ai/sessions/9aff071b2f6a4e8fb9a66bbcd0818359