Default sort does not apply existing users

[PythonGermany]

Describe the bug

The documentation here is inconsistent with the application behaviour:

Note that if a user has already sorted the dashboard by a different field, the default sort will not be applied unless the user clears their browser's localstorage.

What do you see?

Once a user has visited the site for the first time they will not receive any application wide sort and filter default value changes until they clear their browser's localstorage.

What do you expect to see?

The server side global config changes are not applied anymore for a user ONLY after they manually changes their local defaults via the UI elements which in turn stores them in localstorage.

List the steps that must be taken to reproduce this issue

1. Visit site with clear localstorage
2. Change application wide default of service via yaml config
3. Visit site again (reload or new tab)
4. Observe how application wide default is not applied

Version

v5.33.0

Additional information

No response

[TwiN]

This is kind of to be expected, because the defaults are just defaults, and once a user configures a preference, we want Gatus to respect that preference.

In a scenario in which there used to be a preference, then the configuration was changed and a new preference was set, is it really the right thing to discard the user's preference just because a developer updated the default configuration? What if the user set a sorting option that was neither the old configuration nor the new configuration, is it really the right move to reset their preference just because the configured default changed?

[PythonGermany]

The issue is that currently the values for sort and filter are already written to localstorage once the page is loaded the first time.

It should only happen once the user manually changes config values via the UI (and therefore sets their personal preference), once that happens server side config changes should of course not be applied anymore until the user clears their localstorage. If localstorage is set for a config its value always takes precedence.

[TwiN]

Ok, that makes sense. I had only briefly looked at your PR and initially thought that you removed the persistence of sorting/filtering preferences altogether, but you just removed it for the initial onMounted call