-
Notifications
You must be signed in to change notification settings - Fork 33
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
CKAN 2.10 compatability #98
base: master
Are you sure you want to change the base?
Conversation
Add CKAN 2.10 compatable fucntions in plugin
@@ -302,6 +307,18 @@ def after_update(self, context, data_dict): | |||
del self.resources_to_validate[resource_id] | |||
|
|||
_run_async_validation(resource_id) | |||
|
|||
if ckan_2_10: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This conditional isn't really needed. It's fine to create the functions even if they won't be called.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ThrawnCA On point. I removed that condition.
This PR had no conflicts at the time of review, but now has conflicts to be resolved. Is there any specific reason it wasn't merged at the time with the positive review it had? |
I can only speak for myself and say I'm pretty sure I didn't have write access at the time. It should be possible to create a new branch within this repo, pull in the Keitaro changes, and fix the conflict. |
I'll get onto this, sorry i did not see this before i started to incorporate qld-gov-au 2.10 work (still wip) |
|
Hi @blagojabozinovski , I've tried to correct your branch based off where this was forked from v2.0.0. Sadly you have 38 failing tests https://github.com/ckan/ckanext-validation/actions/runs/12367164030 commit 7a0a12e (HEAD -> keitaronic/ckan-2.10-test, origin/keitaronic/ckan-2.10-test)
commit da28f22
reviewing what you changed: v2.0.0...keitaroinc:ckanext-validation:ckan-2.10 You went by pushing back the split that ckan 2.10 on dataset/resource creates/updates back onto its original function name and it does seem its not fully functional.
I'll try and work on the qld-gov-au fork which has 2.10 working with passing tests into upstream. the biggest issue i'm needing to work through is logic Code below:
|
Adds comparability with CKAN 2.10