Properly index organization when creating a package #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR address the scenario to update an organization
package_count
field when a package is created via the UI. To do this we need to detect whenpackage_update
action is updating the package's state fromdraft
toactive
More Info:
Chaining
package_create
only covers API or CLI scenarios. (Meaning that we are updating an orgpackage_count
when adding a new dataset)However, while creating a package using the UI
package_create
contains adraft
dataset. This means that the call to reindex theowner_org
will not update thepackage_count
attribute sincedraft
datasets are not counted.The change of the package state from
draft
toactive
happens latter in the process when submiting a resource and calling topackage_update
.