Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: python-jsonschema/check-jsonschema
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.11.0
Choose a base ref
...
head repository: python-jsonschema/check-jsonschema
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.13.0
Choose a head ref
  • 17 commits
  • 46 files changed
  • 4 contributors

Commits on Feb 14, 2022

  1. [pre-commit.ci] pre-commit autoupdate (#41)

    updates:
    - [github.com/sirosen/check-jsonschema: 0.10.2 → 0.11.0](0.10.2...0.11.0)
    
    Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
    pre-commit-ci[bot] authored Feb 14, 2022
    Configuration menu
    Copy the full SHA
    58ec889 View commit details
    Browse the repository at this point in the history

Commits on Feb 16, 2022

  1. [vendor-schemas] automated update (#45)

    Co-authored-by: sirosen <sirosen@users.noreply.github.com>
    github-actions[bot] and sirosen authored Feb 16, 2022
    Configuration menu
    Copy the full SHA
    43ac68f View commit details
    Browse the repository at this point in the history

Commits on Feb 19, 2022

  1. Remove --failover-builtin-schema

    This option made more sense prior to the existence of a toolchain to
    ensure that the vendored schemas are kept up-to-date. It was
    potentially useful to try to use the latest schemastore schema and
    failover to the builtin vendored copy.
    
    However, now that there is an automated daily job to update the
    vendored schemas, it's much less likely that there's significant drift
    between the vendored schema and the schemastore copy. In the event
    that there *is* such drift (e.g. a period during which I cannot
    perform a release), users can still download the latest schema and
    apply it themselves.
    
    Because the failover could lead to inconsistent hook behaviors, it was
    removed from the pre-commit hook definitions. Now it is being removed
    from the application altogether.
    sirosen committed Feb 19, 2022
    Configuration menu
    Copy the full SHA
    09fa5a4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8881fc5 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    2d7de17 View commit details
    Browse the repository at this point in the history
  4. Add GitLab CI to hooks

    GitLab CI support including vendoring of that schema.
    The vendoring script now handles values in the catalog which do not
    have hashes saved in the repo, to better handle new hooks.
    sirosen committed Feb 19, 2022
    Configuration menu
    Copy the full SHA
    85f2343 View commit details
    Browse the repository at this point in the history

Commits on Feb 20, 2022

  1. Add Bamboo Spec to hooks

    Also some mild reformatting changes
    - correct capitalization of SchemaStore in hook descriptions
    - add a formatting helper for raw.githubusercontent URLs
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    3d2d806 View commit details
    Browse the repository at this point in the history
  2. Add support for JSON5 files (#46)

    * Add support for JSON5 files
    
    Expand the renovate hook config to cover json5 files, and add
    conditional support for the json5 format whenever 'json5' or 'pyjson5'
    is installed.
    
    The instance loader component is moved from being a standalone module
    to being a subpackage, so that json5 support can be (mostly) isolated
    into a standalone module.
    
    For now, absent support for json5 in `identify`, there's a special
    check for `.json5` as the file extension, to pick up support.
    
    Also, fix the behavior when a BadFileTypeError is raised to use the
    shortened trace (not full error output), so that the new "nice" error
    is rendered in a more friendly way.
    
    * Add Optional Parsers note to readme
    
    This documents how to install JSON5 support for users.
    If other parsers are added (e.g. TOML), then any additional
    documentation would be added in the same section of the readme.
    sirosen authored Feb 20, 2022
    Configuration menu
    Copy the full SHA
    fc18c52 View commit details
    Browse the repository at this point in the history
  3. Bump version and changelog for release

    Bump the version to 0.12.0 and mark the status as "Beta".
    
    Also tweak the bump-version script to better handle the
    vendor-schemas marker comment.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    46de961 View commit details
    Browse the repository at this point in the history
  4. Generate hook config from schema catalog

    Having a single source of truth simplifies maintenance.
    
    Tests ensure that there is a hook for every schema in the catalog, and
    that the catalog is kept alphabetized.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    e3d1942 View commit details
    Browse the repository at this point in the history
  5. Builtin schema choices are picked up from catalog

    Rather than explicitly listing schema choices in helptext, pick them
    up from the catalog keys. Support both `vendor.X` and `X` in the
    `choices`, set an explicit metavar, and list the schemas with their
    `vendor.X` names in the epilog.
    
    Also include custom schemas in the listing (explicitly add them for
    the CLI opts).
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    935ae7b View commit details
    Browse the repository at this point in the history
  6. Update scripting tools to help maintain readme

    The vendored schema list in the readme is now generated as part of the
    script which converts the catalog into pre-commit-hooks config.
    
    Move scripts into a `scripts/` directory to keep the repo root
    cleaner.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    1d99083 View commit details
    Browse the repository at this point in the history
  7. Add support or --check-metaschema

    This option is mutex with `--schemafile` and `--builtin-schema`, and
    indicates that the instancefiles are, themselves, schemas. The correct
    validator is selected and built from the relevant metaschema specified
    by `"$schema"`, and then applied to each file.
    
    As performance is not yet known to be critical, a new validator is
    built per instance when this option is used, ensuring that each
    instance is validated under the correct metaschema when they are not
    all uniform.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    a527f96 View commit details
    Browse the repository at this point in the history
  8. Update hook generation to help build readme

    Hook listing in the readme is autogenerated, to ensure it stays
    up-to-date.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    5659066 View commit details
    Browse the repository at this point in the history
  9. Improve generated readme hook list

    Add spacing and use backticks for the hook names.
    sirosen committed Feb 20, 2022
    Configuration menu
    Copy the full SHA
    cd26917 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    0905bc7 View commit details
    Browse the repository at this point in the history

Commits on Feb 21, 2022

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