updated the start component

[Ugo-X]

closes #17

here is what it looks like

Summary by CodeRabbit

• New Features

  • Enhanced the Start component to display potential winnings and remaining time for game modes.
  • Updated the layout of the Start components in the Home screen for improved visual organization and information clarity.

• User Interface Improvements

  • Replaced the previous game start button with a detailed layout that includes headings and paragraphs for better user understanding.

[vercel]

@Ugo-X is attempting to deploy a commit to the z-korp Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The changes involve updating the Start component to include additional properties for displaying game mode details, such as potential winnings and remaining time. The Home component has been modified to utilize the updated Start component, enhancing the layout and organization of the user interface. These updates aim to provide players with comprehensive information about game modes before starting a game.

Changes

Files	Change Summary
client/src/ui/actions/Start.tsx	Expanded StartProps interface with potentialWinnings and remainingTime. Updated rendering logic and layout.
client/src/ui/screens/Home.tsx	Modified usage of Start components to include new props and improved layout for game modes.

Assessment against linked issues

Objective	Addressed	Explanation
Update Start component structure (17)	✅
Create a new UI layout within the Start component (17)	✅
Update usage in Home component (17)	✅

Poem

In the meadow where games unfold,
A Start so bright, with tales to be told.
Winnings and time, all laid out clear,
Hop in and play, the fun is near!
With every click, let joy take flight,
A rabbit's delight, in day and night! 🐇✨

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 240654e and ae31cd0.

Files selected for processing (2)

• client/src/ui/actions/Start.tsx (2 hunks)
• client/src/ui/screens/Home.tsx (1 hunks)

Additional comments not posted (8)

client/src/ui/actions/Start.tsx (5)

13-14: LGTM!

The new props potentialWinnings and remainingTime are correctly added to the StartProps interface.

The code changes are approved.

---

17-21: LGTM!

The new props potentialWinnings and remainingTime are correctly destructured in the Start component signature.

The code changes are approved.

---

73-74: LGTM!

The conditions for player and game are correctly added to the disabled variable.

The code changes are approved.

---

79-82: LGTM!

The conditions for player are correctly added to the cost variable.

The code changes are approved.

---

85-108: LGTM!

The new props potentialWinnings and remainingTime are correctly incorporated into the rendering logic.

The code changes are approved.

client/src/ui/screens/Home.tsx (3)

186-187: LGTM!

Commenting out the previous Start components is a temporary measure to prevent their execution.

The code changes are approved.

---

188-198: LGTM!

The new layout structure enhances the visual organization of the UI.

The code changes are approved.

---

189-197: LGTM!

The new props potentialWinnings and remainingTime are correctly added to the Start components.

The code changes are approved.

[Cheelax]

Hello, please add a remaining time for the normal games too

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ae31cd0 and bf95345.

Files selected for processing (1)

• client/src/ui/screens/Home.tsx (1 hunks)

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

• client/src/ui/screens/Home.tsx

[Cheelax]

FYI I just discovered you didnt handle the hide of this component when a game is going on :