-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The definition of LooseCookies is too narrow #4205
Comments
Agree. Good first-time issue. |
Hey! Can I work on this? What is to be done exactly? |
* add more types to LooseCookies #4205 * predefine the Union types for LooseCookies * add CHANGES fragment (cherry picked from commit e048934) Co-authored-by: Adam Bannister <[email protected]>
What about |
Would be nice to add test cases for |
@serhiy-storchaka thanks for the note. |
Sure thing |
So I added the extra two types mentioned and added a test for CookieJar.update_cookies. Should I add a test for ClientRequest.update_cookies too or is that unnecessary? |
They use similar but independent code, so testing ClientRequest.update_cookies is not redundant. |
Ok, I'll try find time to add it this evening. Thanks for the feedback |
Fixed, I think. |
Seems both
CookieJar.update_cookies()
andClientRequest.update_cookies()
accept alsoIterable[Tuple[str, Union[Morsel, str]]
andMapping[str, Union[Morsel, str]]
.The definition of
LooseCookies
which does not include the above types is not compatible with existing user code.The text was updated successfully, but these errors were encountered: