Use config schema to ensure valid merging

Created on 15 June 2018, almost 7 years ago
Updated 3 August 2024, 9 months ago

Problem/Motivation

Currently we have a three-way merge method for config. However, it makes no use of configuration schemas and therefore may risk producing non-valid merge results.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada nedjo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States joegraduate Arizona, USA

    Probably worth considering this again now that config schemas and validation are much more established in core.

  • First commit to issue fork.
Production build 0.71.5 2024