Why does setCookie require a URL when a Cookie has its domain and path set?

[issuefiler]

What’s the point? Cookies are filtered out when you do getCookies(url); so really, what is the point?

[awaterma]

I think this would make a good enhancement; we do parse the cookie once it's been passed. I'll bring this up for discussion.

[GrinZero]

I think this is stupid. There are all kinds of data in the cookie. Why do I need to pass other parameters? Do setcookie need any additional parameters?

[awaterma]

Let's try and keep the language in our repository positive, @GrinZero! We explain these standards in our code of conduct here:

https://github.com/salesforce/tough-cookie/blob/30246e6c039f91ca33fab2046ffdf7a2d3d8c33c/CODE_OF_CONDUCT.md#our-standards

Please let me know if you have a pull request or change you would like to submit; we are slowly looking at and working over these issues as time goes on, but would love more help from the community.

[GrinZero]

Sorry, I just want to highlight that this is unreasonable, not to vent my emotions

[awaterma]

I'll try and pick up this issue when I can next @GrinZero; I think @dennismphil got busy with other work, and we left this behind. But I agree; our API should be easier to use, and not require redundant information.