| Summary: | Unexpected error "Bad identifier ?" | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Mike Wilson <Mike_Wilson> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtis.windatt.public, grant_gayed |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Mike Wilson
Those errors are from JSLint. JSLint is used to validate JSON files (see jsLintPlugin.js). In launchPlugin.js .launch files are marked as their own type extending JSON. If you replace the text in that file with valid JSON you get no errors. WebIDE launch configurations are specified in JSON. Eclipse launch configurations (such as Web IDE Application Launch) are specified in XML. So the likely answer is to do nothing as we don't expect people to put Eclipse launch configurations into Orion for editing. cc'ing Grant for comment Agreed, the extension is being overloaded. In the context of Orion, .launch files should be the kind that extend JSON, not XML. I don't think there's anything to do here. Closing report, if anyone disagrees then please reopen. |