Comment 12 for bug 1750894

Question about managing server persistence of grid settings... We have roughly 50 grids in the browser client today with a persist key. More will follow, of course. Do we want to say as a rule every grid gets a matching workstation (or user) setting for persistence?

If Yes, it simplifies the logic, but also means we'll have quite a few settings to add (many of which will likely be ignored, I suspect) and devs will have to add a setting any time a new grid is added.

If No, we'll need to know which grids should get settings by default. We could provide settings for a reasonable subset of the grids or potentially just start with one to act as an example.

If we don't assume every grid has a server side setting, then presumably any grid that does not have a server setting should fall back to local storage?