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

MSC2540: Stricter event validation: JSON compliance #2540

Merged
merged 10 commits into from
May 25, 2020
Merged

MSC2540: Stricter event validation: JSON compliance #2540

merged 10 commits into from
May 25, 2020

Commits on May 13, 2020

  1. Add MSC2540 for stricter validation of event JSON.

    @clokep
    clokep committed May 13, 2020
    Configuration menu
    Copy the full SHA
    7797c18 View commit details
    Browse the repository at this point in the history

  2. Small clarification.

    @clokep
    clokep committed May 13, 2020
    Configuration menu
    Copy the full SHA
    11587a5 View commit details
    Browse the repository at this point in the history

  3. Update wording to avoid demand-style language. 

    Co-authored-by: Travis Ralston <travpc@gmail.com>
    @clokep @turt2live
    clokep and turt2live committed May 13, 2020
    Configuration menu
    Copy the full SHA
    bbbd9c4 View commit details
    Browse the repository at this point in the history

  4. Be clearer about errors and what to do with current room versions.

    @clokep
    clokep committed May 13, 2020
    Configuration menu
    Copy the full SHA
    03588cb View commit details
    Browse the repository at this point in the history

Commits on May 14, 2020

  1. Specify the current stable room versions. 

    Co-authored-by: Travis Ralston <travpc@gmail.com>
    @clokep @turt2live
    clokep and turt2live committed May 14, 2020
    Configuration menu
    Copy the full SHA
    6757c60 View commit details
    Browse the repository at this point in the history

Commits on May 15, 2020

  1. Fix grammar and typos from review. 

    Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
    @clokep @richvdh
    clokep and richvdh committed May 15, 2020
    Configuration menu
    Copy the full SHA
    0b6301a View commit details
    Browse the repository at this point in the history

  2. Clarify the range of valid values.

    @clokep
    clokep committed May 15, 2020
    Configuration menu
    Copy the full SHA
    007c8b5 View commit details
    Browse the repository at this point in the history

  3. Clarify range a bit more.

    @clokep
    clokep committed May 15, 2020
    Configuration menu
    Copy the full SHA
    e5fa76c View commit details
    Browse the repository at this point in the history

Commits on May 19, 2020

  1. Reword how bad values are handled.

    @clokep
    clokep committed May 19, 2020
    Configuration menu
    Copy the full SHA
    f5ebe33 View commit details
    Browse the repository at this point in the history

Commits on May 20, 2020

  1. Give more guidance on how invalid events should be handled. 

    Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
    @clokep @richvdh
    clokep and richvdh committed May 20, 2020
    Configuration menu
    Copy the full SHA
    0771671 View commit details
    Browse the repository at this point in the history