Skip to content
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.

"Unexpected token ILLEGAL" on document Save #33

Closed
matthurne opened this issue Sep 26, 2012 · 3 comments
Closed

"Unexpected token ILLEGAL" on document Save #33

matthurne opened this issue Sep 26, 2012 · 3 comments

Comments

@matthurne
Copy link

If I click "Edit" on a document when viewing the contents of a collection and then click "Save", sometimes I get an "Unexpected token ILLEGAL" error even if I didn't make any changes to the document. Based on the line number called out by the error, this seems to be caused by [ ... ] showing up where it shouldn't.

When viewing such a document in the non-edit view, there is an array field with a large number of values that is collapsed and displayed like:

fieldname: [ ... ],

When I click edit, the field is not collapsed, and is displayed like:

fieldname: [
    {
        anotherfield: "somevalue"
    },
    {
        anotherfield: "somevalue"
    }
][ ... ],

It seems to me that the [ ... ] shouldn't be there.

@bobthecow
Copy link
Owner

So you're seeing both the collapsed ([ ... ]) and uncollapsed versions of the same property?

@matthurne
Copy link
Author

Correct, in the editor the collapsed [ ... ] representation is there just after the literal uncollapsed representation.

@bobthecow
Copy link
Owner

Thanks for reporting this. I've got a fix in for v2.1.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants