Andreas Lind

Ping @stomita, should be a quick little thing to fix?

I just ran into this as well while trying to calculate specificities for parse the Firefox default stylesheet: ```js > require('specificity').calculate(':-moz-any(ul, ol, dir, menu, dl) ul'); [ { selector: ':-moz-any(ul',...

The [css-selector-tokenizer library](https://github.com/css-modules/css-selector-tokenizer) does support the construct, maybe it'd make sense to use that for the initial tokenization? ```js require('css-selector-tokenizer').parse(':-moz-any(ul, ol, dir, menu, dl) ul, :-moz-any(ul, ol, dir, menu, dl)...

@keeganstreet, oh man, I see. Then it's even more complex than I thought. For the thing I'm working on, I ended up [manually exploding all the cases](https://github.com/assetgraph/assetgraph/commit/56c413f1c465f985f6c2226dfeeb910105c1de68). I guess you'll...

~Is this addressing the same need as https://github.com/AndrewKeig/express-validation/pull/127?~ Edit: Sorry, you did specify that :sweat_smile: Please include a test.

I have to admit that I'm not really a fan of dual-purposing the `joi` parameter.

Can you elaborate a bit on the use case for this? And maybe include a unit test or two?

This test proves that it's fine to have other middleware that add properties to the `request` object: https://github.com/AndrewKeig/express-validation/commit/5b8b4015c62c20ef006182a2e5a40df10181e294 ... but I'm probably misunderstanding exactly what it is that you're trying...

I agree that especially for `req.headers` and `req.body`, `Joi.object({})` provides a bit of a rough default when it comes to extra properties. For that reason I've ended up wrapping `express-validation`...

Does it work if you add `script-src 'self' 'unsafe-eval'` to the Content-Security-Policy of the web page (or Chrome Extension or whatever) that you're trying to use exceljs on, as the...