nested nodes

[Evanfeenstra]

We usually DO NOT need nested nodes. functions within functions, or types within functions, are not relevant most of the time, since the agent can just read the parent

no_nested should filter out

• Function in Function
• Datamodel in Function
• Function in Datamodel
• Function in Test

Maybe a good first step is remove nested function in tests? too many mock callbacks are polluting the graph

[fayekelmith]

**patterns we do not have but might need: **

export function useStore() {
  const [state, setState] = useState<StoreState>(initialState);

  const setPeople = useCallback((people: Person[]) => {
    setState((prev) => ({ ...prev, people }));
  }, []);

  const setLoading = useCallback((loading: boolean) => {
    setState((prev) => ({ ...prev, loading }));
  }, []);

  const addPerson = useCallback((person: Person) => {
    setState((prev) => ({
      ...prev,
      people: [...prev.people, person],
    }));
  }, []);

  return {
    state,
    setPeople,
    setLoading,
    addPerson,
  };
}

• We do not currently capture setPeople setLoading and addPerson but we get edges to their calls like : Edge: function-people-srctestingreactsrccomponentspeopletsx-4 - Calls -> function-usestore-srctestingreactsrccomponentspersontsx-18 in -accurate but has something to it.
• component/hook call flow to point to the specific helper, not just the parent hook/function