Cms: Add element index settings to project config

[carlcs]

According to your check list it’s not a bad candidate at least.

[brandonkelly]

Yeah agreed.

[jsunsawyer]

Digging into Project Config right now and came across this when looking for gotchas.

Might be nice if the docs clearly stated everything that's _not_ stored in the project config. Right now it's just a list of everything that's included, and one would assume that it's everything that _should_ be included. https://docs.craftcms.com/v3/project-config.html

[brandonkelly]

and one would assume that it's everything that _should_ be included

That’s the case.

We haven’t added this yet because we decided that element index settings actually shouldn’t be, because eventually each user is going to be able to customize element indexes to their own liking.

[benface]

We haven’t added this yet because we decided that element index settings actually shouldn’t be, because eventually each user is going to be able to customize element indexes to their own liking.

That's cool, but I still think the "default" element indexes (when a user doesn't care, or before they customize them) should be stored in project config.

[brandonkelly]

Saving defaults in project config makes sense.

[benface]

Is this a 3.x thing or probably 4.0? Project config has definitely spoiled me, but it's slightly annoying to have to go in the production site's CP and manually adjust some settings after a deployment, especially when everything else just syncs automatically.

[brandonkelly]

We are going to be making some big changes to element indexes in 4.0, so it makes sense to wait until then.

[benface]

That's what I thought. Thanks!

[mmikkel]

This sounds great, just wanted to emphasise the importance of the developer still being able to configure default index settings, even if each user can override those defaults with their own (and yes, those defaults should be stored in PC) 👍

[brandonkelly]

For sure.