Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

bug in url parsing #304

SierraGolf opened this Issue Apr 18, 2012 · 1 comment


None yet
2 participants

I recently stumbled upon the problem to pass additional data with each request.

I found out that currently there is only one way to do so by adding parameters to the given url.

Now I discovered that the parser or parsing part inside the widget which separates the url and the query and then build up a key/value list which is later put into data object of the actual ajax request does not handle multi value fields correctly.

To be more concrete if you have given an url like http://www.example.com?key[]=value1&key[]=value2 the resulting data to be passed to the ajax request will only contain the last key/value pair.

I would prefer to have a new option which can hold additional data and will pass it to the underlying ajax request so that users do not need to use the hacky GET parameter solution I used.

My current hotfix was to hack the parsing part and make it store multi-values as an array inside the ajax data object.

I am kind of new to this whole github thingy, but I would like to contribute to a solution if that would be ok.

I had the same problem, how did you solved? Do you know if the developers of tokenInput already corrected this bug, or even if this is a bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment