Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how Schema Objects require full-document parsing (3.1.1) #3758

Merged
merged 3 commits into from
May 14, 2024

Commits on Apr 26, 2024

  1. Clarify how Schema Objs require full-doc parsing

    JSON Schema draft 2020-12 includes numerous keywords that require
    parsing the entire document prior to deeming a reference unresolvable.
    This makes that more clear and outlines several approaches.
    
    The practice of embedding OpenAPI fragments in other formats is
    deemed to have implementation-defined (non-interoperable) behavior,
    as the potential complications that might arise are not predictable.
    handrews committed Apr 26, 2024
    Configuration menu
    Copy the full SHA
    9da10c5 View commit details
    Browse the repository at this point in the history

Commits on May 2, 2024

  1. Configuration menu
    Copy the full SHA
    3f60c51 View commit details
    Browse the repository at this point in the history

Commits on May 3, 2024

  1. Rework the guidance around fragmentary parsing.

    This goes into more detail and uses "undefined" instead of
    "implementation-defined" as the behavior is likely to be
    incorrect (rather than just a different interpretationof an
    ambiguous requirement), and may result in security concerns
    as well.
    handrews committed May 3, 2024
    Configuration menu
    Copy the full SHA
    ffe0434 View commit details
    Browse the repository at this point in the history