Closed GoogleCodeExporter closed 9 years ago
It's hard to be sure with this snippet, but looking at it and the stack trace
it seems like the linter is breaking when the file ends with a line that
contains only a tab. I can reproduce it with a file containing only:
swc.pages.photos = function() {};
\t
My guess is that when you concatenate your js files together, the resulting
file doesn't end with a line containing only a tab and the problem goes away.
You can try working around it for now by removing these trailing tabs.
Hopefully we can fix this in the next release of the linter or the one after.
Original comment by a...@google.com
on 3 Mar 2011 at 2:02
Good catch, esp as I just copy-and-pasted the file - next time I'll attach it!
Replacing \n\t[eof] with \n[eof] solves the problem...
(my editor adds the \t, trying to be helpful)
Cheers
Andrew
Original comment by aavmur...@gmail.com
on 3 Mar 2011 at 1:42
Original comment by a...@google.com
on 8 Apr 2011 at 10:05
Original comment by michaelt...@google.com
on 13 Apr 2011 at 8:37
Original issue reported on code.google.com by
aavmur...@gmail.com
on 2 Mar 2011 at 3:24