You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not documented in the changelog so I assume it's not intentional.
The text was updated successfully, but these errors were encountered:
svdm
changed the title
Route data maps merge differently in 0.7.0, breaking compatibility
Route data maps ignore meta-merge in 0.7.0, breaking compatibility
Jun 25, 2024
As a result presumably losing out on the schema merging fixes. (edit: Actually seems to cause more fundamental errors with plumatic schemas, so it's not a practical workaround.)
The root cause of the issue is that update-paths strips metadata from nested maps (strictly: rebuilds the maps from scratch without retaining metadata), preventing meta-merge from ever seeing it, so it's not surprising that meta-merge directives on maps have no effect.
svdm
changed the title
Route data maps ignore meta-merge in 0.7.0, breaking compatibility
Route data maps ignore meta-merge options in 0.7.0, breaking compatibility
Jun 25, 2024
In 0.6.0, nested map data is merged in a way that matches meta-merge, supporting
^:replace
:In 0.7.0, this is no longer the case,
^:replace
is not respected:This is not documented in the changelog so I assume it's not intentional.
The text was updated successfully, but these errors were encountered: