| Summary: | JavaScript problems in plugins/esprima/serializer.js | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Anthony Hunter <ahunter.eclipse> | ||||
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | mamacdon | ||||
| Version: | 4.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Anthony Hunter
Created attachment 234580 [details]
Screen shot of the problem
Here is a screen shot of the problem in Eclipse.
ECMAScript 5 allows reserved words to be used as field names [1], so this code is valid ES5. Unfortunately JSDT's validator does not understand ES5 -- only ES3 -- and that seems unlikely to change anytime soon (see bug 232836). I would recommend turning off the Eclipse JS validation entirely, although I've never been able to figure out how to do this (maybe [2] will help?). [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Reserved_Words#Reserved_word_usage [2] http://www.eclipse.org/forums/index.php?t=msg&th=172311/ (In reply to comment #2) > ECMAScript 5 allows reserved words to be used as field names [1], so this > code is valid ES5. |