DS Tournament Updates

[starknetdev]

• ds tournament on a separate tab
• environment configs used as variables for tournament game queries

Summary by CodeRabbit

• New Features

  • Introduced Dark Shuffle Tournament functionality
  • Added new tournament-related environment variables
  • Updated leaderboard and menu displays to support tournament mode

• Changes

  • Modified tournament GraphQL endpoint
  • Updated screen navigation to include tournament screen
  • Refined tournament visibility and rendering logic

• Removed

  • Removed previous tournament overview component
  • Simplified menu structure related to tournament display

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
loot-survivor	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 22, 2025 4:45pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces changes to support a new "Dark Shuffle Tournament" feature across multiple frontend components. The modifications include updating network configurations, adding environment variables, and modifying UI components to handle tournament-specific logic. The changes primarily focus on integrating tournament functionality into the application's navigation, leaderboard display, and screen management, with new conditional rendering based on tournament activation status.

Changes

File	Change Summary
ui/src/app/components/leaderboard/SeasonTable.tsx	Added logic to handle Dark Shuffle Tournament display, including new environment variable checks and updated tournament title rendering
ui/src/app/containers/AdventurerScreen.tsx	Removed DSTournamentOverview component and related tournament menu logic
ui/src/app/hooks/useUIStore.ts	Updated ScreenPage type to include new "tournament" option
ui/src/app/lib/networkConfig.ts	Updated tournamentGQLURL for mainnet to a new GraphQL endpoint
ui/src/app/page.tsx	Added tournament-related imports, menu items, and screen rendering logic

Sequence Diagram

sequenceDiagram
    participant User
    participant MainPage
    participant MenuItems
    participant Screen
    
    User->>MainPage: Navigates to application
    MainPage->>MenuItems: Check tournament activation
    alt Tournament Active
        MenuItems-->>MainPage: Return tournament menu items
    else Tournament Inactive
        MenuItems-->>MainPage: Return default menu items
    end
    
    User->>MainPage: Selects menu item
    MainPage->>Screen: Update screen state
    alt Screen is Tournament
        Screen->>Screen: Render DSTournamentOverview
    else Other Screen
        Screen->>Screen: Render corresponding component
    end

Loading

Possibly related PRs

• Integrate Dark Shuffle Tournament #290: The changes in this PR directly relate to the integration of the "Dark Shuffle Tournament," which aligns with the new features introduced in the main PR regarding tournament handling and display logic.

Poem

🏆 A Tournament of Pixels Bright 🐰
Dark Shuffle comes with coding might
Menus dance, screens unfurl
A rabbit's code begins to swirl
Tournament dreams take digital flight! 🚀

---

📜 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 0f9e89e and 6882a6c.

📒 Files selected for processing (5)

• ui/src/app/components/leaderboard/SeasonTable.tsx (2 hunks)
• ui/src/app/containers/AdventurerScreen.tsx (1 hunks)
• ui/src/app/hooks/useUIStore.ts (1 hunks)
• ui/src/app/lib/networkConfig.ts (1 hunks)
• ui/src/app/page.tsx (5 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.