Store element overview view settings in database as default

[jurriaanr]

While I like that every user has the option to adjust the view to their liking, as a developer I also have an opinion on what the best view settings for specific elements is. Some should have a link for example, but when I use the api headless the link is only used by the consumer and is not for use by an editor. I like some of the default views to be more clean to start with and leave non relevant columns out.

Right now the view settings are stored client side in the browser local storage. My idea would be to be able to store the default settings for each view in the database. If the user does not have an entry in the local storage it will make one, using the default settings. The admin should also have the options (through settings, or account management) to set a flag to removes the saved views, so that new view settings are loaded.

[thupsi]

Hello! See here: #18041

[jurriaanr]

Oh great! (last week even, i did search, I promise 🙈) Thank you.