Ace runs a jslint/jshint script on the code in the editor, and puts up warnings on lines that don't pass. Unfortunately, it finds things like "const", "let", destructuring assignment, list comprehensions, etc. If we can't get it to not show warnings/errors for this syntax that is valid, perhaps we should turn it off until there is an analyzer that can work with it.
Priority: -- → P2
Target Milestone: --- → Builder 0.9.6
Target Milestone: Builder 0.9.6 → Builder 0.9.7
Target Milestone: Builder 0.9.7 → Builder 0.9.8
The guys from jsHint are on this, moving to the next milestone until I hear word that it is done.
Target Milestone: Builder 0.9.8 → Builder 0.9.9
Target Milestone: Builder 0.9.9 → Builder 0.9.12
Target Milestone: Builder 0.9.12 → Builder 1.0
This is now fixed in the live version of ACE.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Has anybody retained a code sample that was failing?
Example keywords that errored: const, or let...
I tried those and couldn't replicate it - I was expecting something more complicated! This is verified fixed then.
The more recent versions of ACE to correctly identify these keywords, we should upgrade soon.
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.