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.

Sign up for GitHub

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

Jump to bottom

Clarify data model types and formats #4045

Merged
merged 9 commits into from
Aug 27, 2024
Merged

Clarify data model types and formats #4045

merged 9 commits into from
Aug 27, 2024

Commits on Aug 20, 2024

  1. Clarify data model types and formats

    @handrews
    handrews committed Aug 20, 2024
    Configuration menu
    Copy the full SHA
    99b0fd8 View commit details
    Browse the repository at this point in the history

Commits on Aug 21, 2024

  1. Use older JSON spec consistently. 

    Co-authored-by: Ralf Handl <[email protected]>
    @handrews @ralfhandl
    handrews and ralfhandl authored Aug 21, 2024
    Configuration menu
    Copy the full SHA
    c589651 View commit details
    Browse the repository at this point in the history

Commits on Aug 22, 2024

  1. Improve table, make section for formats 

    We had an anchor present for data type formats, but without
a section headering.  At this point, there is enough
information to have a section heading.

Also took @mikekistler's suggestion on flipping the first two
table columns, and tried "JSON Data Type" as a compromise
between "Data Model Type" and "Instance Type".
    @handrews
    handrews committed Aug 22, 2024
    Configuration menu
    Copy the full SHA
    898949f View commit details
    Browse the repository at this point in the history

  2. Merge branch 'v3.1.1-dev' into pr/4045

    @ralfhandl
    ralfhandl committed Aug 22, 2024
    Configuration menu
    Copy the full SHA
    2bc4e48 View commit details
    Browse the repository at this point in the history

  3. Sync with registry. 

    Co-authored-by: Mike Kistler <[email protected]>
    @handrews @mikekistler
    handrews and mikekistler authored Aug 22, 2024
    Configuration menu
    Copy the full SHA
    4b8378a View commit details
    Browse the repository at this point in the history

  4. Use "JSON data types" consistently where relevant. 

    Co-authored-by: Mike Kistler <[email protected]>
    @handrews @mikekistler
    handrews and mikekistler authored Aug 22, 2024
    Configuration menu
    Copy the full SHA
    1c8f451 View commit details
    Browse the repository at this point in the history

Commits on Aug 23, 2024

  1. More tweaks about integers.

    @handrews
    handrews committed Aug 23, 2024
    Configuration menu
    Copy the full SHA
    0b94cf5 View commit details
    Browse the repository at this point in the history

Commits on Aug 26, 2024

  1. Clarifications from mikekistler on OAS data type vs JSON schema kwd/f… 

    …mt restrictions


Clarifies that OAS data modeling is based on the types in the `type` validation keyword, but JSON Schema keywords and formats apply (or not) based on the JSON instance data model, which does not include integers.

Co-authored-by: Mike Kistler <[email protected]>
    @handrews @mikekistler
    handrews and mikekistler authored Aug 26, 2024
    Configuration menu
    Copy the full SHA
    151f316 View commit details
    Browse the repository at this point in the history

Commits on Aug 27, 2024

  1. Update versions/3.1.1.md

    @ralfhandl
    ralfhandl authored Aug 27, 2024
    Configuration menu
    Copy the full SHA
    8f626a5 View commit details
    Browse the repository at this point in the history