Errors reported don't clear on file edit/save
Issue #310
resolved
I am working with the new Lightning Component support, and noticed that if you have an error in your .cmp file, and save it the errors are correctly reported in the Problems tab. But if you fix it, the problems don't go away in the tab, even though the file saves successfully.
Comments (6)
-
repo owner
-
repo owner
Can you provide an example of the type of error that's not being removed. I tried a few things such as invalid element/attribute names and the reported error was properly removed. My guess is that it's something that's not being associated with a file properly, so a reproducible case would be very helpful. Lightning error reporting is quite different from error reporting for other metadata types so it's possible I've missed a case here.
-
repo owner
- edited description
- changed status to resolved
I believe this should be resolved for the most part, and where errors do still hang around, I believe that
#172is the right solution. Resolving this but please let me know if I'm still missing a particular use case. -
repo owner
- changed component to Lightning (Aura)
-
repo owner
- removed version
Removing version: Unassigned (automated comment)
-
repo owner
- changed component to Aura
- Log in to comment
Good to know. Lightning errors are reported quite differently than errors for other metadata types. This one should be easy to reproduce and fix, though. I'll see if I can work it into the first patch for the new Lightning stuff. Keep 'em coming!