-
Notifications
You must be signed in to change notification settings - Fork 209
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
Implement loose mode for cookie jars #56
Implement loose mode for cookie jars #56
Conversation
This might not be needed if request/request#1811 gets merged, but just in case we want to provide this functionality anyways... |
Nice, yes, this is needed. If we're going to change the signature of function CookieJar(store, options) {
if (typeof options === 'boolean') {
options = { rejectPublicSuffixes: options };
}
// ...
this.rejectPublicSuffixes = options.rejectPublicSuffixes Could you also document the change in |
Implemented. It's not quiiite backwards compatible since before you didn't have to pass a boolean arg and it'd still work. Locally it seems like master failed before this, which also now causes the PR to fail. This seems to not be a case on Travis though?! |
Did you update vows locally? I bumped to using 0.8.1 on master. Aside: TODO: stop using vows 😉. It was a good choice at the time tough-cookie was created, but I find the simplicity/stability of mocha (or even TAP) to be qualitatively, and opinionatedly, better. |
Yep, that was it. Successful here too then 👍 |
Implement loose mode for cookie jars
Oops, hold on, didn't push something so will re-merge. |
ok, should be good. will publish as 2.2.0 shortly |
Published! Thanks again @Sebmaster, you rock! |
Nice, hopefully I can finally put this 2 year old bug I found to bed 😀 |
* Prep for prerelease, LWC to 0.37.4 * platformResourceLoader mocks return promise * expectedApiVersion to 46.0 * jest@24.8.0 * 0.5.0 * update CHANGELOG * Upgrade LWC to 0.37.4-220.2, remove deasync (#56) * Remove deasync section of README
Forgot that this might be needed too, especially if tough-cookie is used in conjunction with
request
, which doesn't set loose by default.I was thinking about doing an options object as a param instead, but I don't think that the already existing option can be replaced in a backwards-compatible way, so we could only add an options object in addition. Not sure about what to do here.