chore: replaced copy for meta preview

Hugo0 commented 3 months ago

@borcherd

is src/components/Create/Link/Confirm.view.tsx and src/components/Create/Link/Input.view.tsx okay with this change?
Why do we have the the same code in 10+ places? Should we maybe standardize this or is it a bad idea?

Summary by CodeRabbit

New Features
- Updated page descriptions across multiple sections to emphasize "Text Tokens" instead of "Send crypto via link," indicating a shift in focus and branding.
- Enhanced clarity in user interface components related to link creation, aligning terminology with new branding.
Bug Fixes
- Improved user instructions for link creation to enhance understanding and streamline the process.
- Expanded support information to include EU accounts in the account type descriptions.

vercel[bot] commented 3 months ago

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

Name	Status	Preview	Comments	Updated (UTC)
peanut-ui	❌ Failed (Inspect)			Aug 9, 2024 7:54pm

coderabbitai[bot] commented 3 months ago

Walkthrough

The recent updates across various files signify a rebranding initiative, transitioning the terminology from "Send crypto via link" to "Text Tokens." This semantic change in the metadata descriptions enhances clarity and aligns the application's messaging with its new features. Components have also been refined for improved user experience, ensuring consistency and intuitiveness in language as it relates to user actions.

Changes

File Path	Change Summary
`src/app/*/page.tsx`	All pages updated `description` from "Send crypto via link" to "Text Tokens," reflecting a new focus.
`src/components/Create/Link/*.view.tsx`	Labels and descriptions in `CreateLinkConfirmView` and `CreateLinkInputView` changed to "Text Tokens," clarifying user actions.
`src/components/Claim/Link/Initial.view.tsx`	Updated account support message from "US and IBAN" to "US and EU," expanding the scope of supported accounts.

Poem

In fields of code, where rabbits play,
"Text Tokens" bloom, brightening the way.
No more links for crypto to send,
A new path unfolds, around the bend.
So hop along, dear friends, with glee,
Embrace the change, let it be free! 🐇✨

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

borcherd commented 2 months ago

is src/components/Create/Link/Confirm.view.tsx and src/components/Create/Link/Input.view.tsx okay with this change?

Why do we have the the same code in 10+ places? Should we maybe standardize this or is it a bad idea?

Metadata should be set specifically per page, but yes we can create consts out of those values. @Hugo0

Hugo0 commented 2 months ago

Well then maybe correct solution is to change the page Metadata instead? And add specific titles to all our pages

peanutprotocol / peanut-ui