You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to have their personal preference for developer settings but storing cfg to Cookie as persistent state each time it changes and restore on session start (login)
This shall be simply ui side implementation by some js magic - no backend api changes
The text was updated successfully, but these errors were encountered:
I think it might be even easier to do this with localStorage. Or at least, I personally prefer using localStorage over cookies, for browser-side preferences. You'd need to think about the situation where backend defaults change though, would the backend administrator want that to override user preferences? And could JS errors became a possibility if the settings types changed?
Yes, local storage is even better.
Defaults -by reset to default as an option clickable formally settings would leave control to the user.
Downwards compatible api changes is alway a good pattern 😄
Allow users to have their personal preference for developer settings but storing cfg to Cookie as persistent state each time it changes and restore on session start (login)
This shall be simply ui side implementation by some js magic - no backend api changes
The text was updated successfully, but these errors were encountered: