feat: mediaWiki change dump dir!

[amindadgar]

Summary by CodeRabbit

• Refactor
  • Updated the storage location for dumps to use a nested "dumps" directory structure for improved organization.

[coderabbitai]

Walkthrough

The change updates the initialization of the dump_dir attribute in the MediawikiETL class. Instead of storing dumps in a directory named with the pattern "dump_{community_id}", the directory path is now set to "dumps/{community_id}", introducing a new parent "dumps" directory. Corresponding test setup, teardown, and assertions were updated to reflect this new directory structure. No other logic, control flow, or public interfaces were modified.

Changes

File(s)	Change Summary
hivemind_etl/mediawiki/etl.py	Changed dump_dir initialization from "dump_{community_id}" to "dumps/{community_id}".
tests/unit/test_mediawiki_etl.py	Updated test setup, teardown, and assertions to use "dumps/{community_id}" directory path instead of "dump_{community_id}".

Poem

In the warren of folders, a new path appears,
"dumps" is the burrow where each dump now steers.
No more lonely directories, just neat little rows,
Where each community’s data quietly grows.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8576181 and f414749.

📒 Files selected for processing (1)

• tests/unit/test_mediawiki_etl.py (2 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

tests/unit/test_mediawiki_etl.py (1)

hivemind_etl/mediawiki/etl.py (1)

• MediawikiETL (11-93)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: ci / test / Test
• GitHub Check: ci / lint / Lint

🔇 Additional comments (4)

tests/unit/test_mediawiki_etl.py (4)

18-19: Directory structure change looks good

The setup now correctly creates the new directory structure with a parent "dumps" directory containing the community-specific directory, which aligns with the implementation change in MediawikiETL.

---

23-24: Consistent teardown implementation

The teardown method correctly cleans up the community-specific directory under the new path structure. One minor consideration: while the community directory is cleaned up, the parent "dumps" directory remains. This is generally acceptable as it's a common practice to keep parent directories, but worth noting.

---

32-32: Assertion updated correctly

The assertion correctly verifies that the dump_dir attribute is set to the new path format.

---

49-49: Mock assertion updated correctly

The test correctly verifies that the crawler is called with the updated dump directory path.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.