Group duplicate errors

[benogle]

atom/atom#4472

Maybe something like a counter would be nice?

[OJFord]

Has there been any progress on this?

It's incredibly painful. Especially when the error is in core; not a plugin that can be disabled. Even when it's a plugin, often they're still usable and desirable even without whatever's broken.

This just seems like something that should so obviously be the case, and just a simple matter of programming I'm sure... 😉 I may take a look later in the week.

Just to emphasise how silly this is; this is the work of a few seconds, because right now I get an error every keypress:

I've sectioned off the whole area with an empty pane so I can just leave them there, but what a waste.

[tomduncalf]

@OJFord my work around is to hide the errors with CSS: atom/atom#8152 (comment)

[ericclemmons]

Here's my dilemma:

• Finished working on a project. Ready to prepare for deployment!
• rm -rf node_modules
• NODE_ENV=production npm i (no more eslint-* or other dev-tools!)
• npm run build (It failed!)
• I open up Atom to start correcting files, removing dev-only code, etc., but all I see is:

  https://cloud.githubusercontent.com/assets/320562/9020155/7e4c4588-382f-11e5-95d5-0a319dcb2c1b.png

• I "Close All", but every new file throws things errors up.

My recommendation is:

• Be able to ignore notifications that only lasts for the current session/project. Restarting Atom, or closing the window resets it.

[joshwcomeau]

What's the progress on this? Currently dealing with this, every time I hit a key:

I'm fine with the error (broken linting is not top priority), but the error messaging is making it impossible to work :/

[saizai]

+1. I think this would also substantially address the UX issues in: #116 #88 #90