-
Notifications
You must be signed in to change notification settings - Fork 4
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
Calculate additional codelist values for schema using anyOf #137
Conversation
@jpmckinney I wanted to simplify the tests, so we didn't also have to change the check for local or remote schemas. Does this still capture the change you are after? |
The integration.yml changes from #125 are relevant - otherwise these tests will forever fail. The change to Edit: Indeed - As for the test, if it fails without the changes to common.py (and passes with the changes), then that's what matters. |
It's on my todo list and I was going to look at separately
Noted in seperate issue to check out - thanks.
It does! |
@jpmckinney - @Bjwebb has pointed out the comments are anyOf but the code is oneOf - it should be doing this for both right? If so I can just add this and we should be done:
|
I probably meant oneOf everywhere (OCDS doesn't use anyOf), but supporting anyOf should be the same logic, so that change sounds good. |
335a586
to
079a67c
Compare
… like OCDS record packages #125 open-contracting/lib-cove-ocds#106
079a67c
to
6ef4f9f
Compare
Added. I don't think we need a special test just for that elif - if I change schema_with_oneof_codelists.json locally I can see it working for anyOf too. But over to @Bjwebb to review! |
Like OCDS record packages
#125 open-contracting/lib-cove-ocds#106