-
Notifications
You must be signed in to change notification settings - Fork 85
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
fix: Base URI for jsonschema.RefResolver has better behavior #1976
Conversation
Codecov ReportBase: 98.24% // Head: 98.24% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #1976 +/- ##
=======================================
Coverage 98.24% 98.24%
=======================================
Files 68 68
Lines 4378 4378
Branches 726 726
=======================================
Hits 4301 4301
Misses 45 45
Partials 32 32
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I'm going to go ahead and use my admin powers to merge this in so we fix up the main branch. |
@kratsg this is breaking the Minimum supported dependencies workflow. Line 44 in 925769a
and Line 63 in 925769a
are now failing (c.f. https://github.com/scikit-hep/pyhf/runs/8148172028?check_suite_focus=true). I'll see if I can identify the version of Line 41 in 925769a
and Line 5 in 925769a
to. edit: I'm assuming it is |
… v1.4.0 (#1979) * Update lower bound of the supported jsonschema versions to v4.15.0 to use the required improvements to jsonschema.RefResolver used in PR #1976. - c.f. https://github.com/orgs/python-jsonschema/discussions/995 - Amends PR #1976. * Update lower bound of the supported importlib-resources versions to v1.4.0 as > jsonschema 4.15.0 depends on importlib-resources>=1.4.0; python_version < "3.9" * Update tests/constraints.txt to use jsonschema==4.15.0 and importlib_resources==1.4.0.
Pull Request Description
jsonschema
has traditionally been not the greatest with resolving references. More recent development has definitely aimed to improve this behavior (thanks to @Julian) and it seems it highlighted an issue with how we defined ourRefResolver
. This PR moves theversion
up to thebaseuri
instead of being part of the document name.Resolves #1975.
Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: