Only show lint warnings from most recently edited file in browser console

[gaearon]

This came up in discussion in #2070 (comment).
Seems like a sensible thing to do, although I'm not sure how hard it would be.

Tagging as good first bug but I don't have any ideas on how to do it.

[siggirh]

I'm wondering if this helps with the complaint from tnrich in that linked thread. If the developer is commenting out stuff or w/e, saving and looking back to the browser - the changes (and thus, the output that annoys him) is going to come from that last edited file. Aren't those errors the ones he doesn't want to see in the console?

[gaearon]

We can cap it to maximum 5 warnings per file, for example. They would still be there but they would be more relevant, and limited.

[siggirh]

Wouldn't that be confusing if you have more than five and are only displaying five of them? As in, wouldn't capping the number defeat the purpose of having them there in the first place? I guess my pondering is whether displaying the linting errors in the console is to let the user know that he HAS errors or that he has these EXACT errors. I'm wondering if we should leave this alone and let it stay as is :)

[gaearon]

We can debate whether to cap them or not, but I think displaying them just for most recently edited file is a good start by itself.

[svicalifornia]

@gaearon @kombucha Has the commit referenced above been merged into the official CRA trunk?

[kombucha]

@svicalifornia Nope, see #2409

[gaearon]

Not yet. We'll do a cleanup pass some time after releasing React 16. For now most of my effort is focused on React.