Right now the config sync process is all or nothing, which means that if a user sees come config they want to import and some they don't (and/or some they don't understand why its being listed) then they have to sort it all out before syncing.
It would probably be relatively easy to change this so that the user selects exactly what pieces of config they want to import. This would go a long way to improving the UX of the config system, because even if the user encounters some changes they don't expect or understand in addition to the ones they do expect, they can choose the ones they are ready for an figure the rest out later.
While this isn't difficult to implement in the UI, the dependency chain can be a nightmare for certain types of config (most notably stuff associated with the field system.) Some potential solutions:
- Config owned by certain modules can't be cherrypicked
- Add a metadata key indicating whether the piece of config can be cherrypicked (would rely on happening)