I made this a debounce function to prevent the case where a user rapidly presses on a component and triggers this callback in rapid succession as the user profile bottom sheet comes into view. When this happens it could cause a render error due to too many re-renders. Adding the 500ms debounce delay here gives the navigator enough time to navigate to the user profile bottom sheet w/o any issues

_debounce forces a delay. I think you want _throttle

I guess leading: true might be more like _throttle? If so, can you clarify the differences?

Yea you are right _throttle is going to be better here. The difference between throttling and debouncing is that the timer for the delay will reset every time the debounced function is called. Throttling won't do that. On the user's end it won't really make a difference, but will update to _throttle since that is technically more right

https://css-tricks.com/the-difference-between-throttling-and-debouncing/#aa-debouncing-enforces-that-a-function-not-be-called-again-until-a-certain-amount-of-time-has-passed-without-it-being-called-as-in-execute-this-function-only-if-100-milliseconds-have-passed-witho

I made this a throttled function to prevent the case where a user rapidly presses on a component and triggers this callback in rapid succession as the user profile bottom sheet comes into view. When this happens it could cause a render error due to too many re-renders. Adding the 500ms throttle delay here gives the navigator enough time to navigate to the user profile bottom sheet w/o any issues

Yes confirmed that the opening + closing animation of the bottom sheet > 500ms, so by the time the user does a round trip the throttle delay will be over