James Ross

> This would be safer and more readable: > > ```js > queues.a.find(filter, job => { > console.log(job); > }); > ``` That still throws a `unicorn/no-array-callback-reference` - it's the...

> I think we could detect this case by only triggering the error if there's one argument (since the `thisArgument` on the actual array methods is rarely used). That would...

Pages using `wrangler.toml` locally but not when you publish _really_ confuses people. We see it every single week in the Discord. https://github.com/cloudflare/workers-sdk/issues/3757 It seems a little strange to me to...

I left [a comment](https://github.com/cloudflare/workers-sdk/issues/3757#issuecomment-1917332954) on the `workers-sdk` PR, but I'm personally not sure this reduces confusion. 🤷‍♀️ Leaning into what has been considered a bug for years, with everyone being...

I think it would be extremely beneficial to hold this PR until it's made very clear in `wrangler pages deploy` commands and Pages CI that publishing a project with bindings...

I'm no longer able to reproduce this - it seems to be resolved.

This is a great suggestion, thank you! I'll have to have a think about the API I want to implement for each of these, since unfortunately we can't easily get...

Something like that should work great, yes! There's unfortunately also not a way to efficiently check if an asset exists yet either (though I'm regularly encouraging the team to add...

Looks like the same issue as in https://github.com/cloudflare/wrangler2/issues/2240

Thanks @dario-piotrowicz. I did miss some tests, good catch! I agree it would be good to only quote when needed. I originally opted for consistency, since that's what I personally...