Skip to content

plan.Diagnostic carries no source position #21

Description

@tdakkota

plan.Diagnostic has {Pointer, Severity, Message} — a JSON Pointer string and nothing else.

ogen reports errors with file, line and column via location.Pointer, and recently improved exactly this (fix(libopenapi): attach source positions to parse errors). A generator consuming plans would lose that, making the migration a visible regression in error quality.

libopenapi keeps *yaml.Node positions on the low-level model, so the frontend can capture line/column at conversion time and thread them onto every diagnostic. Also needs a document/file identity once multi-document loading is in play (external $ref targets already come from other documents).

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions