-
Notifications
You must be signed in to change notification settings - Fork 207
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
URI encode the cursorMark value before use #166
Conversation
URI encoding needed because cursorMark raw value can contain characters not allowed without uri encoding
URI encode the cursorMark value before use
Nice catch. Thanks @flawless2011 |
No problem. Any chance we can get a 0.6.1 release out to npm @nicolasembleton ? |
Yes. Let me work that out. Been away for a while but need to get back at it seriously. Let's try to get one done within the coming 2 weeks. Will create a separate thread. |
@nicolasembleton Any update on pushing a 0.6.1 to npm registry? |
Lunar new year slowed me down. Will try to consolidate and push this week On Fri, Jan 29, 2016 at 1:42 AM Derek Lawless notifications@github.com
|
Do you have an open issue on the doc updates? |
Not yet. Want to participate? If yes I'll make one to make it easier to On Tue, Feb 2, 2016 at 4:30 AM Derek Lawless notifications@github.com
|
I'll do what I can to contribute. |
Thanks Derek. On Tue, Feb 2, 2016 at 11:55 PM Derek Lawless notifications@github.com
|
URI encoding needed because cursorMark raw value can contain characters not allowed without uri encoding. Closes #165