You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded and included v1.3.0 to handle cookies in my web application.
However, the cookie variable that is declared in your README.md is undefined. When I roll back to v.1.2.2, the documentation matches what is written.
In the v1.3.0 cookies.js file, the proper usage is in the comments.
Why the change from cookie to docCookies? In addition, the javascript filenames are different: cookie.js in v1.2.2 compared with cookies.js in v.1.3.0. It feels like things are completely different between these two versions.
It is inconsistent and there is no explaination for it and github documentation doesn't reflect the update. Did you release the wrong code?
It's been approximately 4 years since the release of v1.3.0. I would ask that at a minimum, the README.md would be updated to reflect the newest version's api or a reversion to the previous api and naming along with whatever non-naming updates added in v.1.3.0.
I really like the naming and structure of v1.2.2 so I'd prefer to stick with that.
The text was updated successfully, but these errors were encountered:
I downloaded and included v1.3.0 to handle cookies in my web application.
However, the
cookie
variable that is declared in your README.md is undefined. When I roll back to v.1.2.2, the documentation matches what is written.In the v1.3.0 cookies.js file, the proper usage is in the comments.
Why the change from
cookie
todocCookies
? In addition, the javascript filenames are different:cookie.js
in v1.2.2 compared withcookies.js
in v.1.3.0. It feels like things are completely different between these two versions.It is inconsistent and there is no explaination for it and github documentation doesn't reflect the update. Did you release the wrong code?
It's been approximately 4 years since the release of v1.3.0. I would ask that at a minimum, the README.md would be updated to reflect the newest version's api or a reversion to the previous api and naming along with whatever non-naming updates added in v.1.3.0.
I really like the naming and structure of v1.2.2 so I'd prefer to stick with that.
The text was updated successfully, but these errors were encountered: