FIX(#330): Remove useCallback hook from auth context provider

[chris-nowicki]

fixes #330

Removed useCallback function from AuthContextProvider.tsx as it was not needed and it's dependencies causing more renders than needed.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gridiron-survivor	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 16, 2024 6:23pm
gridiron-survivor-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 16, 2024 6:23pm

[appwrite]

Gridiron Survivor Application 6616ea581ef9f5521c7d

Function	ID	Status	Action
Your function deployment has failed. Please check the logs for more details and retry.

Project name: Gridiron Survivor Application
Project ID: 6616ea581ef9f5521c7d

Function	ID	Status	Action
userAuth	6626fef885a9f630442b	Failed	View Logs

Only deployments on the production branch are activated automatically. If you'd like to activate this deployment, navigate to your deployments. Learn more about Appwrite Function deployments.

💡 Did you know?
Cursor pagination performs better than offset pagination when loading further pages

[choir241]

LGTM, but do you have any screenshots of any of your tests so we can see what's happening after you removed useCallback()?

[ryandotfurrer]

ezpz LGTM

[chris-nowicki]

LGTM, but do you have any screenshots of any of your tests so we can see what's happening after you removed useCallback()?

I do not have screenshots. What happens is the page still loads without issues :). Really it is a behinds the scene change.

[vmaineng]

As always, your beautiful pieces of code gone. :) I'd love to know how you found out useCallback was causing more rendering. :)