feat: update mediaWiki platform & modules schema!

[amindadgar]

Summary by CodeRabbit

• Bug Fixes

  • Improved handling of platform activation status, ensuring only activated platforms with defined namespaces are processed.
  • Enhanced warning messages to clearly indicate when a platform is skipped due to missing namespaces or deactivation.

• Tests

  • Updated test cases to reflect the new activation flag logic.
  • Added a test to verify that only activated platforms are included in the results.

[coderabbitai]

Walkthrough

The changes update the logic for retrieving MediaWiki platform metadata in the ETL module. The code now fetches the namespaces property directly from the platform's metadata store and introduces a check for an activated flag before processing each platform. Only platforms marked as activated and with available namespaces are included in the results. In the test suite, the structure of test data was adjusted to reflect the new separation of activated and namespaces between module and platform metadata, and a new test was added to verify the filtering of deactivated platforms. Additionally, tests for website modules were updated to include the activated flag in inserted module documents. The tc-hivemind-backend package version was also updated.

Changes

File(s)	Change Summary
hivemind_etl/mediawiki/module.py	Updated to retrieve namespaces from platform metadata and to skip processing platforms not marked as activated.
tests/integration/test_mediawiki_modules.py	Adjusted test data to match new metadata structure; added test for filtering out deactivated platforms.
tests/integration/test_module_website.py	Added "activated": True field to inserted module documents in multiple test cases.
requirements.txt	Updated tc-hivemind-backend package version from 1.4.2.post2 to 1.4.3.

Sequence Diagram(s)

sequenceDiagram
    participant ETL_Module
    participant Platform_Metadata_Store
    participant Logger
    participant Results_List

    loop For each platform
        ETL_Module->Platform_Metadata_Store: get_platform_metadata(platform_id)
        Platform_Metadata_Store-->>ETL_Module: metadata (includes namespaces)
        ETL_Module->ETL_Module: Check 'activated' in module metadata
        alt Not activated
            ETL_Module->Logger: Log warning and skip platform
        else Activated
            ETL_Module->ETL_Module: Check for 'namespaces'
            alt Namespaces missing
                ETL_Module->Logger: Log warning and skip platform
            else Namespaces present
                ETL_Module->Results_List: Append platform data
            end
        end
    end

Loading

Possibly related issues

• Feat: MediaWiki, update platform and module configs! #27: This PR implements the retrieval of namespaces from platform metadata and adds an activate/deactivate flag, directly addressing the objectives described in the issue.

Poem

In the warren of code, new checks now appear,
Only platforms awakened may hop into the clear.
Namespaces are fetched from the right little nook,
While sleepy ones skipped with a warningly look.
Tests now ensure that the rules are precise—
Only the lively are counted, which is rather nice!
🐇✨

---

📜 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 b9b29cb and b5341fc.

📒 Files selected for processing (1)

• tests/integration/test_mediawiki_modules.py (8 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/integration/test_mediawiki_modules.py

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

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

---

🪧 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.