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

Comments

nedjo created an issue. See original summary.

nedjo’s picture

nedjo
he/him/his
Primary language English
CreditAttribution: nedjo commented
Status: Active » Postponed

An initial look suggests config schemas are not yet sufficient or mature enough to provide a reliable guide here.