unicorn/no-fn-reference-in-iterator mistaking .find method?

I’m using a third-party API that contains a method called find. It is not find as in the collection find, but rather their own find. It expects a scalar value (id) and then does its thing.

XO is throwing the following error:

✖   82:41  Do not pass function directly to .find(…).  unicorn/no-fn-reference-in-iterator

Given that the parameter is scalar, how could this happen? Sample code:

const clientId = 20
const client = await oidc.Client.find(clientId)

If this is still a valid application of the rule, what would the correct code look like? The rule doc explains the code could be wrapped in an arrow function, which does pass the text. But, is this right?

const clientId = 20
const client = await oidc.Client.find(() => clientId)

[sindresorhus]

I think we can exclude any await’ed expression.

[fisker]

One second, what if

const promises = [p1, p2, p3];

const isP2 = p => p === p2;

const foo = await promises.find(isP2)

?