$.removeCookie(cookieName) about jquery-cookie HOT 9 CLOSED

But isn't consistent with the jQuery style of overloading methods.

It also seems to be inconsistent in itself with how a cookie is written. If at all there should then be a addCookie function along with removeCookie.

from jquery-cookie.

I may disagree with you. See the following example:

$().attr("id", "myID")
$().removeAttr("id")

There is no $().addAttr

removeCookie is much more intuitive and follow jquery's style

from jquery-cookie.

@carhartl Did you thought about this? Seriously I think it is a very good feature and it does'nt add so many chars =(

from jquery-cookie.

Nearly convinced.

from jquery-cookie.

$.removeCookie = function(name, options) {
    $.cookie(name, null, options);
};

from jquery-cookie.

Do u think the options are needed here?
My idea here is simulate the "options.expires = -1" by aliasing $.cookie("name", null) to $.removeCookie for the sake of readability
You may probably be able to do this without testing all the stuff $.cookie does, but I don't think the performance improvement would be noticeable

from jquery-cookie.

I think yes, it's required. You can only remove the cookie with the same options (path and domain options are the important ones here) that were used to write it in the first place. Basically removing the cookie is nothing else than a write.

You could have written a cookie for different paths:

$.cookie('foo', 'bar', { path: '/one' });
$.removeCookie('foo', { path: '/one' });

$.cookie('foo', 'bar', { path: '/two' });
$.removeCookie('foo', { path: '/two' });

Of course passing options isn't necessary when relying on the default options.

from jquery-cookie.

Don't think performance is a real issue here, unless you're deleting 1000 cookies in a row maybe.

from jquery-cookie.

Let's consider #87 on this one

from jquery-cookie.