scratch
/bower_components/js-cookie/README.md |
@@ -94,6 +94,8 @@ |
|
*IMPORTANT! when deleting a cookie, you must pass the exact same path and domain attributes that was used to set the cookie, unless you're relying on the [default attributes](#cookie-attributes).* |
|
*Note: Removing unexisting cookie does not raise any exception nor return any value* |
|
## Namespace conflicts |
|
If there is any danger of a conflict with the namespace `Cookies`, the `noConflict` method will allow you to define a new namespace and preserve the original one. This is especially useful when running the script on third party sites e.g. as part of a widget or SDK. |
@@ -142,7 +144,7 @@ |
|
This project is [RFC 6265](http://tools.ietf.org/html/rfc6265#section-4.1.1) compliant. All special characters that are not allowed in the cookie-name or cookie-value are encoded with each one's UTF-8 Hex equivalent using [percent-encoding](http://en.wikipedia.org/wiki/Percent-encoding). |
The only character in cookie-name or cookie-value that is allowed and still encoded is the percent `%` character, it is escaped in order to interpret percent input as literal. |
Please note that the default encoding/decoding strategy is meant to be interoperable [only between cookies that are read/written by js-cookie](https://github.com/js-cookie/js-cookie/pull/200#discussion_r63270778). To override the default encoding/decoding strategy you need to use a [converter](#converter). |
Please note that the default encoding/decoding strategy is meant to be interoperable [only between cookies that are read/written by js-cookie](https://github.com/js-cookie/js-cookie/pull/200#discussion_r63270778). To override the default encoding/decoding strategy you need to use a [converter](#converters). |
|
## Cookie Attributes |
|
@@ -271,6 +273,10 @@ |
|
Check out the [Contributing Guidelines](CONTRIBUTING.md) |
|
## Security |
|
For vulnerability reports, send an e-mail to `jscookie at gmail dot com` |
|
## Manual release steps |
|
* Increment the "version" attribute of `package.json` |
@@ -279,9 +285,9 @@ |
* Create version tag in git |
* Create a github release and upload the minified file |
* Change the `latest` tag pointer to the latest commit |
* `git tag -fa latest` |
* `git tag -f latest` |
* `git push <remote> :refs/tags/latest` |
* Commit with the message "Prepare for the next development iteration" |
* `git push origin master --tags` |
* Release on npm |
|
## Authors |