| Summary: | Incorrect 'missing semicolon' warning in case of for-in loop | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Maciej Bendkowski <maciej.bendkowski> | ||||||
| Component: | JS Tools | Assignee: | Mark Macdonald <mamacdon> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | mamacdon.bugs, mamacdon | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 5.0 M1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
Created attachment 237787 [details]
Validation error - warning
|
Created attachment 237786 [details] Validation error - code After changing our default JS validator to ESLint, I've notice an incorrect 'missing semicolon' warning in some of mine for-in loops (see attachments).