Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unexpected token ILLEGAL" on document Save #33

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

"Unexpected token ILLEGAL" on document Save #33

mhurne opened this issue Sep 26, 2012 · 3 comments

Comments

@mhurne
Copy link

@mhurne mhurne commented Sep 26, 2012

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

@bobthecow bobthecow commented Sep 26, 2012

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

@mhurne
Copy link
Author

@mhurne mhurne commented Sep 27, 2012

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

@bobthecow bobthecow closed this in 235b0dd Sep 27, 2012
@bobthecow
Copy link
Owner

@bobthecow bobthecow commented Sep 27, 2012

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.