Reputation: 20244
When loading a json file (validated with json.bloople.net) starting as follows:
{
"sepString": "--",
into an ExtJS JsonPStore, Chrome returns the following error:
Uncaught SyntaxError: Unexpected token : in line 2
What does Chrome try to tell me?
EDIT:
When loading the json file
{
"globalSettings" : [{
}]
}
into an ExtJS JsonPStore, Chrome returns the following error:
Uncaught SyntaxError: Unexpected token : in line 2
What does Chrome try to tell me?
Upvotes: 2
Views: 526
Reputation: 20244
JsonP != Json, as Evan Trimboli pointed out in a comment, providing a link to the extensive ExtJS JsonP proxy documentation.
Upvotes: 0
Reputation: 4355
I think we possibly need more code to answer however, if your data is as follows:
{
"sepString": "--",
}
This appeared to work in json.bloople.net however this is not valid json because of the comma. You can try with jsonlint.com and it will generate the error...
Parse error on line 2:
...String": "--", }
---------------------^
Expecting 'STRING'
Upvotes: 4