If devs open the lib directory in Atom directly, Dart analyzer doesn't run
collinjackson opened this issue · comments
I'm not sure if this is possible to fix, but I've seen people run into this issue and we might want to detect this case and indicate what's going on.
Feel free to close as invalid if you disagree.
If it's common enough, we can warn about it at runtime and tell the user they'll have a better experience opening the parent dir.
Runtime warning would be a good solution IMO. It's confusing because the syntax highlighting still works, so it looks like Atom is doing something intelligent, but it's not being as helpful as it should be.
Atom is enough of a text editor that users will think they can do this (it's common to open a single file in sublime, e.g.).
There's a general issue: users are confused when some things work, but others don't. If they have the Flutter plugin installed, I think we can be more forceful when everything isn't working correctly. I'd love to see a more obvious "something is wrong" notice to developers, even if some things are working.
This issue was moved to flutter/flutter#1474