i often use past/future tense stuff for dirty-flag type operations - thoughts? didChange, willCleanup.

@sw-yx Ah yes, forgot about those. They make sense too.

Seems this could be generalized as sort of like core id-match, but applied to specific types. Configuration could look something like:

{
    "typescript/typed-id-match": [
        "error",
        { "types": [/* ... */], "pattern": "^(is|has|can|did|will)$" },
        { /* ... */ }
    ]
}

Should this rule deal with properties? How to deal with property names you cannot control, for example, other people's api?

// it probably does not make sense to warn on this
const options = {capture: true, passive: false};
someExternalApi(options);

Does this rule cover boolean valued functions?

There's no reason the rule couldn't support all of these things and have options to enable/disable checks.

Side note: Another possible prefix that may be considered is should. This is very semantically similar to will, but in some cases I find should the more fitting choice (e.g. when used as a function parameter).

As an example from the code that induced this comment:

function formatArray(data: any[], shouldIgnoreEmpty = false) {
  if (data.length === 0 && shouldIgnoreEmpty) {
    return ''
  } else {
    return JSON.stringify(data)
  }
}