fix(wiki): updated mods wiki site

[TobiTenno]

What did you fix?

fix missed mods update path

---

Reproduction steps

---

Evidence/screenshot/link to line

Considerations

• Does this contain a new dependency? [No]
• Does this introduce opinionated data formatting or manual data entry? [No]
• Does this pr include updated data files in a separate commit that can be reverted for a clean code-only pr? [Yes]
• Have I run the linter? [Yes]
• Is is a bug fix, feature request, or enhancement? [Bug Fix]

Summary by CodeRabbit

• Refactor
  • Enhanced the organization of tradable item categories, distinguishing mod options from general items for a clearer trading experience.
  • Updated the source for mod data retrieval to ensure the latest information is consistently displayed.

[coderabbitai]

Walkthrough

This pull request restructures the definitions of tradable item types. In the build/tradable.mjs file, specific mod types are extracted into a new array (tradableMods), and the main tradableTypes array is updated to include both existing types and the mod types via the spread operator. Additionally, in the build/wikia/scrapers/ModScraper.mjs file, the URL used in the ModScraper superclass constructor is updated from a fandom domain to a wiki domain.

Changes

File	Change Summary
build/tradable.mjs	Separated mod types into a new tradableMods array and updated tradableTypes to include general types plus ...tradableMods.
build/wikia/scrapers/ModScraper.mjs	Updated the URL in the ModScraper constructor from https://warframe.fandom.com/wiki/Module:Mods/data?action=edit to https://wiki.warframe.com/w/Module:Mods/data?action=edit.

Sequence Diagram(s):

Suggested labels

released

Suggested reviewers

• EricSihaoLin
• SlayerOrnstein

Poem

I'm a hopping rabbit, swift and spry,
Restructuring code as I leap high.
Mods and types now dance in line,
A cleaner merge, a design so fine.
With every change, my joy's complete—
🐇 Hopping through code, can’t be beat!

---

📜 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 98b1dbc and 8692c6c.

📒 Files selected for processing (1)

• build/tradable.mjs (1 hunks)

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

• build/tradable.mjs

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

• GitHub Check: Build

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 19b09a8 and 98b1dbc.

📒 Files selected for processing (2)

• build/tradable.mjs (1 hunks)
• build/wikia/scrapers/ModScraper.mjs (1 hunks)

🧰 Additional context used

🪛 ESLint

build/tradable.mjs

[error] 20-29: Replace ⏎··'Arcane',⏎··'Captura',⏎··'Cut·Gem',⏎··'Fish',⏎··'Focus·Lens',⏎··'Relic',⏎··'Upgrades',⏎··...tradableMods,⏎ with 'Arcane',·'Captura',·'Cut·Gem',·'Fish',·'Focus·Lens',·'Relic',·'Upgrades',·...tradableMods

(prettier/prettier)

🪛 GitHub Check: Lint

build/tradable.mjs

[failure] 20-20:
Replace ⏎··'Arcane',⏎··'Captura',⏎··'Cut·Gem',⏎··'Fish',⏎··'Focus·Lens',⏎··'Relic',⏎··'Upgrades',⏎··...tradableMods,⏎ with 'Arcane',·'Captura',·'Cut·Gem',·'Fish',·'Focus·Lens',·'Relic',·'Upgrades',·...tradableMods

🪛 GitHub Actions: Pull Request Checks

build/tradable.mjs

[error] 20-20: Replace ⏎··'Arcane',⏎··'Captura',⏎··'Cut·Gem',⏎··'Fish',⏎··'Focus·Lens',⏎··'Relic',⏎··'Upgrades',⏎...tradableMods,⏎ with 'Arcane',·'Captura',·'Cut·Gem',·'Fish',·'Focus·Lens',·'Relic',·'Upgrades',·...tradableMods prettier/prettier

🔇 Additional comments (2)

build/wikia/scrapers/ModScraper.mjs (1)

6-6: URL update looks good

The URL change from fandom.com to wiki.warframe.com is appropriate and aligns with the PR objective of fixing the update path for mods. The Warframe Wiki has likely moved from the Fandom domain to its own domain, so this change is necessary to ensure the mod data is scraped from the correct source.

build/tradable.mjs (1)

4-19: Good separation of mod types into dedicated array

Creating a separate tradableMods array for mod-specific types improves code organization and maintainability. This approach makes it easier to update just the mod types if needed in the future.

[wfcd-bot-boi]

🎉 This PR is included in version 1.1267.73 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀