[WEB-2813] chore: improved the cascading logic#6152
Conversation
WalkthroughThe changes involve modifications to the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
apiserver/plane/bgtasks/deletion_task.py (1)
22-24: Consider extracting the condition to improve readabilityWhile the current implementation is correct, the multiple condition checks could be extracted into a helper function to improve readability and reusability.
Here's a suggested refactor:
+def has_cascade_delete(field): + return ( + hasattr(field, "remote_field") and + hasattr(field.remote_field, "on_delete") and + field.remote_field.on_delete == models.CASCADE + ) + @shared_task def soft_delete_related_objects(app_label, model_name, instance_pk, using=None): # ... existing code ... for field in related_fields: if field.one_to_many or field.one_to_one: try: - if ( - hasattr(field, "remote_field") and - hasattr(field.remote_field, "on_delete") and - field.remote_field.on_delete == models.CASCADE - ): + if has_cascade_delete(field):
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
apiserver/plane/bgtasks/deletion_task.py(1 hunks)
🔇 Additional comments (1)
apiserver/plane/bgtasks/deletion_task.py (1)
22-24: LGTM! More robust attribute checking
The new implementation is more defensive and explicit in checking the existence of attributes before accessing them. This prevents potential AttributeError exceptions and makes the cascading logic more reliable.
chore:
Summary by CodeRabbit