Fix all storage containers reindexed when other add-ons are upgraded#54
Merged
Fix all storage containers reindexed when other add-ons are upgraded#54
Conversation
xispa
changed the title
ramonski
approved these changes
Oct 15, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of the issue/feature this PR addresses
This Pull Request optimizes the upgrade process to ensure that only the required import steps are executed when other add-ons are upgraded.
Current behavior before PR
Upgrading another add-on triggers a reindexing of all sample storage containers, even when unnecessary.
Desired behavior after PR is merged
Upgrading another add-on runs only the necessary import steps, preventing redundant reindexing.
--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.