Michał Gołębiowski-Owczarek

For pure JS code the easiest way to solve issues with nested ternaries is to stop using them in favor of `if`+`else`. It's not that easy with TypeScript, though, as...

**Comment author: dmethvin** I'm sympathetic, but a Google search usually helps. I'm not sure the additional words there add much to it, and any attempt to add "Sizzle" or "jQuery"...

**Comment author: walde.christian@…** a Google search usually helps The usability here is similar to having a numerical error code to google. Unless one has seen the message before and know...

**Comment author: timmywil** We could change "expression" to "selector", but it seems pretty clear to me as the selector itself is included in the error message.

**Comment author: walde.christian@…** it seems pretty clear to me as the selector itself is included in the error message Please take a look at my original description again. When this...

**Comment author: timmywil** How about something concise like 'Error: Selector Syntax: .flag' ?

**Comment author: walde.christian@…** I'm fine with shortening it, but for maximum benevolence towards future users i'd like to see explicit mention of CSS remain in the message. :)

**Comment author: timmywil** I thought about that, but then I remembered that there are still some users out there who use XPath converters, in which case the selector was not...

**Comment author: dmethvin** I'm okay with the suggestion in comment 5, with minor formatting changes: Error in selector syntax: .flag We'll need to announce this prominently so that when people...

**Comment author: walde.christian@…** This is merely an observation: If you are concerned that people will not understand what an error message means and will need to google it, then the...