FIX : Changing settings requires refreshing the page to apply #490

[fawez9]

This PR fixes the issue where changing a setting like smoothCharts didn’t update the dashboard until you refreshed the page.
I wrapped smoothCharts in React state at the provider level, so the dashboard now updates immediately when the setting changes. Cookies are still used to persist your preferences, and SSR continues to work as expected. I also added a small DashboardWrapper to make sure SSR props and client-side context stay in sync.
How to test: toggle smoothCharts in your settings — the dashboard updates instantly. Refresh the page, and the cookie keeps your preference.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
testaustime	Ready	Preview, Comment	Dec 17, 2025 9:18pm
testaustime-storybook	Ready	Preview, Comment	Dec 17, 2025 9:18pm

[Chicken]

Build fails for eslint errors

[fawez9]

Everything is good now I think !

[Eldemarkki]

There are still some checks failing, could you revert the changes in package-lock.json and try again? I'll check the code later today

[fawez9]

Check it now I think problem solved !

[Eldemarkki]

Now it only updates the smooth charts setting, it should update all settings. I tested a bit myself and you can move the useSettings hook into Dashboard.tsx and get rid of the getPreferences() calls. That way there's no need for the DashboardWrapper either.

[fawez9]

i did some changes check them out when you're free and tell me if anything is not as needed , also what's the problem on the deployment here ?

[Chicken]

Type error, Property 'defaultDayRange' does not exist on type 'IntrinsicAttributes & DashboardProps'.

[fawez9]

Hi @Eldemarkki , I’ve implemented the assignment check as discussed and tested it locally.
Happy to adjust anything if needed — thanks!

[fawez9]

I kept my focus on the settings changes we discussed (useSettings / removing getPreferences & DashboardWrapper).
I noticed some language-related behavior in the dashboard, but I didn’t touch i18n since I wasn’t sure if it’s in scope.

[Eldemarkki]

@fawez9 I will check it this evening when I have time

[Eldemarkki]

I'll merge this now, thank you for your first contribution!