This is because useNavigate isn't the type, it is the function being called. allowForKnownSafeCalls operates on the type, and in this case, that is NavigateFunction (since useNavigate(): NavigateFunction)

if you set "name": "NavigateFunction", it will work

maybe that's just a docs thing or maybe the rule should operate on symbol names instead

Aha, thank you! I think this is what @bradzacher mentioned ... somewhere, I forget - that the selector only works on types, not values, at the moment. Edit: no, I misread - this is working as intended.

Good question on whether this is a bug or a docs issue. IMO this is a bug because we want to let users specify allowed known safe functions. The specifier is even called "type or value specifier". cc @typescript-eslint/triage-team

The issue isn't just that though.

The promise doesn't come from the useNavigation function. It comes from the navigate function. That function is locally defined so it will never match the selector you've configured.

Put another way - your config should prevent flagging on

useNavigation();

But not on

const cb = useNavigation();
cb(); // error here

Though still this option operates on types right now and useNavigation isn't that

That is possibly still an issue if we want the rule option to also allow allowing of symbol names rather than only types

FYI @JoshuaKGoldberg #10660 also/already tracks matching values with TypeOrValueSpecifier. Seemingly, though, since that won't solve this issue, what remains on this issue is more of a "what should be done about patterns that can't easily be matched by a type/value selector?"

what should be done about patterns that can't easily be matched by a type/value selector?

Ideally the libraries return some nominally typed promise that a user can match the rule on - which was what we tried to push people to.

Alternately PromiseLike is currently ignored by the rule as per other issues because of its existing usages in such APIs.

Yeah I don't know that there's a way for us to do anything here. As mentioned in #10686 (comment), targeting the NavigateFunction name itself does work in this report:

"@typescript-eslint/no-floating-promises": ["error", {
    "allowForKnownSafeCalls": [
        { "from": "package", "name": "NavigateFunction", "package": "react-router" }
    ]
}]

Closing out as non-actionable. Thanks all!