Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The client-side
List
objects were storing a ton of duplicated and unnecessary data.Here's what one of the Admin UI
List
objects looked like before:Notice how not only was the entire
adminMeta
object duplicated in every list, but theconfig
object was being saved despite beingassigned
ed to theList
object. This meant that the entire config object was being saved twice, and it also meant completely unnecessary keys likeviews
were being saved too (these are used by the field view loader and aren't needed here).This removes the copy of
adminMeta
(it wasn't used anywhere) and theconfig
copy + assignment in favor of explicitly picking out the pieces ofconfig
we want to save. Note this does mean the raw field config is no longer accessible atlist.config.fields
, but it's still available via the field controller inlist.fields
.Lot cleaner!