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.

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

QGOV cleanup as per #57 #67

Merged
merged 2 commits into from
Jul 29, 2022
Merged

QGOV cleanup as per #57 #67

merged 2 commits into from
Jul 29, 2022

Conversation

ThrawnCA
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Jul 29, 2022

Codecov Report

Merging #67 (636aab9) into master (cd06189) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #67      +/-   ##
==========================================
+ Coverage   82.67%   82.70%   +0.03%     
==========================================
  Files          26       26              
  Lines        2147     2157      +10     
==========================================
+ Hits         1775     1784       +9     
- Misses        372      373       +1     
Impacted Files Coverage Δ
ckanext/validation/logic.py 68.66% <100.00%> (ø)
ckanext/validation/plugin/__init__.py 97.18% <100.00%> (-0.55%) ⬇️
ckanext/validation/utils.py 100.00% <100.00%> (ø)

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@amercader amercader merged commit f151aa5 into ckan:master Jul 29, 2022
amercader added a commit that referenced this pull request Oct 27, 2022
In async mode, if a dataset already has one or more resources suitable
for validation, when adding a new one all the previous ones are also
sent to validate.

@ThrawnCA patch in #67, dealt with the same scenario but when updating
an existing resource.

In this case sadly we need to use the context, as there is no way to
reliably tell in `after_update` if it's part of a resource_create call
amercader added a commit that referenced this pull request Dec 1, 2022
In async mode, if a dataset already has one or more resources suitable
for validation, when adding a new one all the previous ones are also
sent to validate.

PR #67 dealt with the same scenario but when updating
an existing resource.

In this case sadly we need to use the context, as there is no way to
reliably tell in `after_update` if it's part of a resource_create call
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants