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
When ajax() is called, JSON.stringify is called again. This causes the string to get double encoded. For example: "{\"name\":\"ted\",\"age\":22}" Parsing that on the server turns into a string instead of an object.
I've created an example comparison between jQuery and jquip. Look at the payloads.
As for a solution, is the call to JSON.stringify necessary? It doesn't match the behavior of jQuery's ajax().
The text was updated successfully, but these errors were encountered:
Backbone's invocation of ajax() passes data that has been stringified.
When ajax() is called, JSON.stringify is called again. This causes the string to get double encoded. For example:
"{\"name\":\"ted\",\"age\":22}"
Parsing that on the server turns into a string instead of an object.I've created an example comparison between jQuery and jquip. Look at the payloads.
As for a solution, is the call to JSON.stringify necessary? It doesn't match the behavior of jQuery's ajax().
The text was updated successfully, but these errors were encountered: