Skip to content

[Rendering] R0: change list and builder #956

Open
0 of 5 issues completed
Open

Description

@DrSatyr

Part of the rendering plan: #954 (R0)

Goal

Turn the result tree into a flat list of change records once. Nothing uses it yet.

Scope

One item per PR:

  • Store the old/new $ref on ChangedSchema (the engine knows it, but doesn't keep it today)
  • Change record (rule, result, operation, location, component, pointer, change, old, new, message) and ChangeReport (model only)
  • Builder: generic walk over getChangedElements(), plus operation-level changes (parameters, request/response bodies, responses, headers, security, extensions, examples, operation metadata)
  • Builder: schema changes (properties, enum, type, bounds, required, readOnly/writeOnly, …)

Verdicts are copied from the result tree; no rule changes. rule and result are owned by #724.

Done when

Activity

  1. added this to the 3.0.0 milestone on Nov 15, 2026
  2. added theissue type on Nov 15, 2026
  3. Inf1mum commented on Nov 16, 2026

    @Inf1mum

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions