javascript: a handler that reaches a component through React context or redux connect props has no use, and path calls the two independent #1751

A function that reaches a component through React context or redux connect props has no use in the graph, so the component that hands it to a JSX attribute never shows up. Seen in a real redux app (5 this.props.onX handlers) and in a context-based auth app.

// Auth.jsx
const Ctx = createContext(null);
export function Provider({ children }) {
  const logout = () => 'out';
  return <Ctx.Provider value={{ logout }}>{children}</Ctx.Provider>;
}
export function LogoutButton() {
  const { logout } = useContext(Ctx);
  return <button onClick={logout}>out</button>;
}
// Settings.jsx
function Settings(props) { return <button onClick={props.onClickLogout}>out</button>; }
const mapDispatchToProps = (dispatch) => ({
  onClickLogout: () => dispatch({ type: 'LOGOUT' }),
});
export default connect(null, mapDispatchToProps)(Settings);

• impact src/Auth.jsx:4 (logout): lists only Provider [hop 1], not LogoutButton.
• path LogoutButton src/Auth.jsx:4: "the two are independent in this graph… no unresolved site would connect them".
• impact src/Settings.jsx:4 (onClickLogout): lists only mapDispatchToProps [hop 1], not Settings.

Expected: LogoutButton and Settings list the handler as handed over (registered), the same way a directly imported onClick={logout} does. At the least, path should report the unresolved useContext destructure instead of saying the two are independent.