Community
Participate
Working Groups
If your Javascript file contains an error that causes JSLint to give up parsing completely, you will not see any error messages in the UI. 1. Create a new JavaScript file 2. Enter some gibberish and save. For example: > %^&!*foo 3. A TypeError is thrown by the Orion UI (see below), but no error markers are produced. TypeError arguments: Array[2] 0: "substring" 1: undefined message: "—" stack: "—" type: "non_object_property_call" AnnotationFactory.showProblems() at editorFeatures.js:113 exports.setUpEditor.mOutliner.Outliner.parent() at setup.js:453 EventTarget.dispatchEvent() at serviceregistry.js:185 internalRegistry.dispatchEvent() at serviceregistry.js:266 ServiceRegistration.dispatchEvent() at serviceregistry.js:94 ProblemService._setProblems() at problems.js:31 Service.addEventListener() at serviceregistry.js:127 eclipse.SyntaxChecker.SyntaxChecker.checkSyntax() at syntaxchecker.js:65 notify() at Deferred.js:171 dojo.Deferred.then.promise.then() at Deferred.js:269 eclipse.SyntaxChecker.SyntaxChecker.checkSyntax() at syntaxchecker.js:64 ...
There was a problem with some code in editorFeatures.js that worked around a quirk in jslint's data format. Moved it to jslintPlugin and fixed the error. http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=13d756a16a565abbd600e3c75ce81b7cd09865d3