Community deletion

[NolanTrem]

Important

Enhance error handling and add community deletion functionality in graphs.py, with minor refactoring in conversations.py and management_service.py.

• Error Handling:
  • Use contextlib.suppress for json.JSONDecodeError in graphs.py for cleaner error handling.
  • Add from e to raise HTTPException for better exception chaining in graphs.py.
• Functionality:
  • Add delete_all_communities method in PostgresCommunitiesHandler in graphs.py to delete all communities for a given parent_id.
  • Update reset method in PostgresGraphsHandler to use delete_all_communities.
• Refactoring:
  • Remove unused import KGEnrichmentStatus in graphs.py.
  • Minor import reordering in conversations.py and management_service.py.

^{This description was created by for b49dacc. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to b49dacc in 59 seconds

More details

• Looked at 332 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. py/core/database/graphs.py:971

• Draft comment:
  The new method delete_all_communities is a good addition for handling bulk deletions of communities associated with a parent_id. This improves code clarity and reusability.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR introduces a new method delete_all_communities in PostgresCommunitiesHandler to delete all communities for a given parent_id. This method is used in reset method of PostgresGraphsHandler.

2. py/core/database/graphs.py:131

• Draft comment:
  Using contextlib.suppress(json.JSONDecodeError) is a cleaner approach than try-except for ignoring JSON decode errors. This change is applied consistently across the file.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR replaces try-except blocks with contextlib.suppress for JSONDecodeError, which is a cleaner approach for handling exceptions when the intent is to ignore them.

3. py/core/database/graphs.py:321

• Draft comment:
  Using raise ... from e for exception chaining provides better context for debugging. This change is consistently applied across the file.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR modifies exception handling to use raise ... from e for better exception chaining, which is a good practice for debugging.

4. py/core/database/graphs.py:950

• Draft comment:
  The delete method now accepts an optional community_id, allowing for targeted deletions. This enhances the method's flexibility.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR modifies the delete method in PostgresCommunitiesHandler to accept an optional community_id parameter, allowing for more flexible deletion operations.

5. py/core/database/graphs.py:1179

• Draft comment:
  The reset method now uses delete_all_communities, aligning with the new method addition for bulk community deletions.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The PR modifies the reset method in PostgresGraphsHandler to use the new delete_all_communities method, which aligns with the new method addition.

Workflow ID: wflow_HmuUITKIxefaWAHx

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.