scratch – Diff between revs 58 and 125

Subversion Repositories:
Rev:
Show entire file – Ignore whitespace
Rev 58 Rev 125
Line 92... Line 92...
92 Cookies.remove('name', { path: '' }); // removed! 92 Cookies.remove('name', { path: '' }); // removed!
93 ``` 93 ```
Line 94... Line 94...
94   94  
Line -... Line 95...
-   95 *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).*
-   96  
95 *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).* 97 *Note: Removing unexisting cookie does not raise any exception nor return any value*
Line 96... Line 98...
96   98  
Line 97... Line 99...
97 ## Namespace conflicts 99 ## Namespace conflicts
Line 140... Line 142...
140   142  
Line 141... Line 143...
141 ## Encoding 143 ## Encoding
142   144  
143 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). 145 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).
Line 144... Line 146...
144 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. 146 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.
Line 145... Line 147...
145 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). 147 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).
Line 269... Line 271...
269   271  
Line 270... Line 272...
270 ## Contributing 272 ## Contributing
Line -... Line 273...
-   273  
-   274 Check out the [Contributing Guidelines](CONTRIBUTING.md)
-   275  
-   276 ## Security
271   277  
Line 272... Line 278...
272 Check out the [Contributing Guidelines](CONTRIBUTING.md) 278 For vulnerability reports, send an e-mail to `jscookie at gmail dot com`
273   279  
274 ## Manual release steps 280 ## Manual release steps
275   281  
276 * Increment the "version" attribute of `package.json` 282 * Increment the "version" attribute of `package.json`
277 * Increment the version number in the `src/js.cookie.js` file 283 * Increment the version number in the `src/js.cookie.js` file
278 * Commit with the message "Release version x.x.x" 284 * Commit with the message "Release version x.x.x"
279 * Create version tag in git 285 * Create version tag in git
280 * Create a github release and upload the minified file 286 * Create a github release and upload the minified file
281 * Change the `latest` tag pointer to the latest commit 287 * Change the `latest` tag pointer to the latest commit
Line 282... Line 288...
282 * `git tag -fa latest` 288 * `git tag -f latest`
Line 283... Line 289...
283 * `git push <remote> :refs/tags/latest` 289 * `git push <remote> :refs/tags/latest`