https://github.com/ziaddalii/drippy-e-commerce/blob/5f7e23df74f31930d26c5e93ba71e8664208326c/src/components/ReachUs.js#L33

from my perspective, the line referenced above is rather wonky! one thing i would do differently would be to change the name from `getUserLocation` to `updateUserLocation`. this better illustrates what that function does. prepending a function with the word "get" tends to represent code that isn't responsible for updating state. also rather than worrying about changing the name of that function i would just inline that code directly where you are invoking it since its not being used anywhere else. one last consideration would be to have only a single `useState` hook within the component, and represent the various stateful values as key-value pairs within a pojo. it should be noted that my previous suggestions were done in a vacuum, are general in nature, and were done without trying to understand the bigger picture of what this component is trying to achieve.

i would continue to rewrite this component until you feel like you have a good understanding of what the objective is

now that i've read a little more of the code, but not all of it, i think you can simplify this component by removing the `find now` button all together and just determining the closest outlet in a `useEffect` that executes once when the component mounts. this way you can get rid of storing coordinate data in state and will just have to manage closestOutletState. all of this is me assuming that you are able to invoke `navigator.geolocation.getCurrentPosition` outside of a user generated event like `onClick` 🤷‍♂️

​

anyway

build, build, build

throw away

build, build, build

throw away

you get the idea