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
Taking the first scope item: storing the old/new `` on ChangedSchema. The change-list/builder items remain open for now.
This is a small, natural extension of the model from #938, which already follows refs into referenced component schemas when checking property type changes — keeping the source refs on the diff result is the same data the engine already handles there, it just isn't retained today.
One question on the last scope line: rule and result are listed as owned by #724, but that issue no longer exists (404). Was it removed in favor of a different tracking place for those two fields? Happy to follow wherever they landed — for this PR they're out of scope either way, since it only adds the two ref fields to ChangedSchema.
Activity
Inf1mum commentedon Nov 16, 2026
Taking the first scope item: storing the old/new `` on
ChangedSchema. The change-list/builder items remain open for now.This is a small, natural extension of the model from #938, which already follows refs into referenced component schemas when checking property type changes — keeping the source refs on the diff result is the same data the engine already handles there, it just isn't retained today.
One question on the last scope line:
ruleandresultare listed as owned by #724, but that issue no longer exists (404). Was it removed in favor of a different tracking place for those two fields? Happy to follow wherever they landed — for this PR they're out of scope either way, since it only adds the two ref fields toChangedSchema.