test rename client fee env

[RedBeardEth]

Summary by CodeRabbit

• New Features

  • Environment variables updated to reflect a new naming convention, changing VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT across multiple configuration files.

• Bug Fixes

  • Ensured that the frontend property in the realm settlement process now references the updated public fee recipient variable.

• Documentation

  • Updated environment variable declarations in sample and production files to align with the new naming convention.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve renaming the environment variable VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT across multiple configuration files, including .env.local.sample, .env.preview, .env.production, and others in both the client and landing directories. This renaming indicates a shift in the variable's scope to make it publicly accessible. Additionally, the frontend property in the SettleRealmComponent and Steps components is updated to reference the new variable name, while the overall logic and functionality of these components remain unchanged.

Changes

File Path	Change Summary
client/.env.local.sample	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
client/.env.preview	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
client/.env.production	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
client/src/ui/components/cityview/realm/SettleRealmComponent.tsx	Updated frontend property from env.VITE_CLIENT_FEE_RECIPIENT to env.VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
client/src/ui/modules/onboarding/Steps.tsx	Updated frontend property from env.VITE_CLIENT_FEE_RECIPIENT to env.VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
landing/.env.production	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
landing/.env.sample	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.
landing/.env.sepolia	Renamed VITE_CLIENT_FEE_RECIPIENT to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.

Possibly related PRs

• env #1973: This PR modifies environment variables in the client/.env.preview file, including the addition of VITE_PUBLIC_CLIENT_FEE_RECIPIENT, which is directly related to the changes in the main PR where VITE_CLIENT_FEE_RECIPIENT is renamed to VITE_PUBLIC_CLIENT_FEE_RECIPIENT.

• [mobile] cannot settle from mobile #2126: This PR updates the SettleRealmComponent.tsx to use VITE_PUBLIC_CLIENT_FEE_RECIPIENT, which is directly related to the changes in the main PR where the variable is renamed.

• implements zod env checking #2138: This PR introduces new environment variables, including VITE_PUBLIC_CLIENT_FEE_RECIPIENT, which aligns with the changes in the main PR regarding the renaming of the variable.

• test update env production #2419: This PR renames VITE_PUBLIC_CLIENT_FEE_RECIPIENT back to VITE_CLIENT_FEE_RECIPIENT, which is a direct modification of the variable discussed in the main PR.

Suggested reviewers

• ponderingdemocritus

Poem

🐰 In fields of green where bunnies play,
A change was made, hip-hip-hooray!
The fee recipient, now public and bright,
Guides our realms in the soft moonlight.
With joy we hop, our code refined,
A brighter path for all to find! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b582ada and 4106e84.

📒 Files selected for processing (8)

• client/.env.local.sample (1 hunks)
• client/.env.preview (1 hunks)
• client/.env.production (1 hunks)
• client/src/ui/components/cityview/realm/SettleRealmComponent.tsx (1 hunks)
• client/src/ui/modules/onboarding/Steps.tsx (1 hunks)
• landing/.env.production (1 hunks)
• landing/.env.sample (1 hunks)
• landing/.env.sepolia (1 hunks)

---

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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
eternum	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 0:56am
eternum-docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 0:56am
eternum-landing	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 11, 2024 0:56am

[mentatbot]

You are out of MentatBot reviews. Your usage will refresh December 16 at 08:00 AM.

[github-actions]

Failed to generate code suggestions for PR