as the title says, it throws an exception (unexpected character) which comes from the fact that IE does not support the array notation for accessing the nth char of a string.
I replaced all str[pos] instances with str.charAt(pos) and it worked like a charm.

an explanation was found here:

Array-like character access (the second way above) is not part of ECMAScript 3. It is a JavaScript and ECMAScript 5 feature.

https://developer.mozilla.org/en/JavaScript/Reference/Global_Objects/String

@vjeux can't see https://github.com/vjeux/URLON/blob/master/src/cycle.js to be used anywhere. Do we need it?

@vjeux
I just found out that we have no License defined for this project.
I'd like to add one but I feel like it is good to consult with you as original author of the code.
My suggestion is to use https://choosealicense.com/licenses/unlicense/ which grants all permissions to a public domain.
Do you agree or do you have any other preference?

Hi all.

I would like to know if there is any RFC about urlon. So... Is there any RFC about urlon? would it be possible to have an RFC from urlon?

I'm thinking of creating a urlon based implementation but with some technical differences or design.

While using this library to update url in my browser I faced an issue while converting it back to JSON.

For example:

urlon.stringify({ foo: 'ba/r' }); // OUTPUT: $foo=ba//r

But in URLs / is a valid character.

Temporarily, I'm using this to solve the problem.

encodeURIComponent(urlon.stringify({ foo: 'ba/r' })); // OUTPUT: %24foo%3Dba%2F%2Fr

It would be great if this issue can be fixed!

undefined values now parse back as string, it potentially could break something:

var obj = { foo: undefined }
assert.deepEqual(parse(stringify(obj)), obj) // fail: { foo: 'undefined' } expected to be { foo: undefined }

I want to fix this as part of 3.0 release since it is could be breaking for someone.

npm requires package name to be all lower cased.
I will deprecate capital cased one.

Currently urlon uses _ to define objects.

URLON.parse('_table_achievement_column=instance&ascending:true')

// Output:  {"table":{"achievement":{"column":"instance","ascending":true}}} 

Underscores are not so uncommon in url params and could be either confusing at first or causing trouble with legacy urls. Maybe there is a way of improving this with an alternate notation pattern.

The first thing that popped into my head was:

URLON.parse('table.achievement.column=instance&ascending:true')
URLON.parse('table.achievement={column:instance,ascending:true')}

That's just phantasy though and hasn't been further evaluated in regards to technical limitations etc.

test runner doesn't work, since some resources is not available.
we need to rewrite tests using runner from npm.