-
Notifications
You must be signed in to change notification settings - Fork 10
replace encode
calls with encodeURIComponent
#4
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
Comments
It would be helpful to know where the bad call(s) are. I did a quick search in the source code and didn't find an error such as Next time it happens could you note the name of the file and the line Dave On Tue, Jul 12, 2016 at 6:07 PM, Don Park [email protected] wrote:
|
Will do. I was thrashing around trying to get things working so didn't capture the details. |
Finally had time to resolve Twitter signin problem that appeared after initially getting the docker working. Turned out to be a typo on my part. At least I can now see the Here is the log output:
function |
Did you have similar Strange part is When I move |
I think issue #3 is caused by this bug, meaning this is a general issue. Steps to replicate error condition:
In my docker branch, I fixed the issue by replacing call to |
I added the workaround in v0.95b. Instead of moving "encode" -- I just call encodeURIComponent in the place that was having the problem. |
lol. that's exactly the change I made in d49420f |
"Great Minds Think Alike." On Wed, Jul 20, 2016 at 9:57 AM, Don Park [email protected] wrote:
|
While dockerizing nodeStorage, I ran into
encode function undefined
error. I did notice that there are several instances ofencode
function sprinkled around in both javascript and OPML files so there error was probably caused by trigger some area not typically covered.Since
encode
function maps directly toencodeURIComponent
, I think they can be replaced with direct calls except in one javascript file whereencode
is defined differently.This is an enhancement only and not required for dockerizing.
The text was updated successfully, but these errors were encountered: