Add givback toast to recrring donations

[MohammadPCh]

• "uncomment" GIVbacks eligible-related frontend pieces that were hidden for superfluid integration #4132

Summary by CodeRabbit

• New Features

  • Added class name customization for GIVBackToast component, allowing for more flexible styling.
  • Enhanced the RecurringDonationCard with new eligibility indicators and a styled GIVBackToast component.

• Improvements

  • Improved user experience by visually indicating GIVBack eligibility on donation cards.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
giveth-dapps-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 25, 2024 3:19pm

[coderabbitai]

Walkthrough

The recent updates bring enhancements to the GIVBackToast and RecurringDonationCard components. Changes include adding a className prop to GIVBackToast, importing GIVBackToast and usePurpleList in RecurringDonationCard, and refining eligibility checks and styled components for improved functionality.

Changes

Files	Change Summary
src/components/views/donate/GIVBackToast.tsx	Added className prop to GIVBackToast component and updated its usage.
src/components/views/donate/RecurringDonationCard.tsx	Imported GIVBackToast and usePurpleList, added eligibility checks, and included a styled GIVBackToastStyled component.

🐰✨
In the land of code, where changes bloom,
New props and hooks dispel the gloom.
With className added, styles take flight,
And eligibility checks ensure all is right.
Donations now toast with a GIVBack cheer,
Purple lists and styled components, oh dear!
🐇💻

Tip

New Features and Improvements

Review Settings

Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments.

AST-based Instructions

CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation.

Community-driven AST-based Rules

We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information.

New Static Analysis Tools

We are continually expanding our support for static analysis tools. We have added support for biome, hadolint, and ast-grep. Update the settings in your .coderabbit.yaml file or head over to the settings page to enable or disable the tools you want to use.

Tone Settings

Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:

• Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!"
• Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!"
• Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!"

Revamped Settings Page

We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to .coderabbit.yaml will be reflected in the settings page, and vice versa.

Miscellaneous

• Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the enable_free_tier setting.
• Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (local) or the organization (global) level using the knowledge_base setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations.
• High-level summary placement: You can now customize the location of the high-level summary in the PR description using the high_level_summary_placeholder setting (default @coderabbitai summary).
• Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the request_changes_workflow setting.

---

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration 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 f7b8573 and 1d4aa5d.

Files selected for processing (2)

• src/components/views/donate/GIVBackToast.tsx (2 hunks)
• src/components/views/donate/RecurringDonationCard.tsx (5 hunks)

Additional Context Used

Biome (8)

src/components/views/donate/GIVBackToast.tsx (1)

16-17: Declare variables separately

src/components/views/donate/RecurringDonationCard.tsx (7)

70-72: This else clause can be omitted because previous branches break early.

---

85-87: This else clause can be omitted because previous branches break early.

---

92-92: Forbidden non-null assertion.

---

237-237: Avoid using target="_blank" without rel="noreferrer".

---

387-387: Unexpected any. Specify a different type.

---

754-754: Forbidden non-null assertion.

---

42-43: All these imports are only used as types.

Additional comments not posted (5)

src/components/views/donate/GIVBackToast.tsx (2)

12-12: Added className prop to enhance styling flexibility.

---

47-47: Properly applied className to ToastContainer for additional styling.

src/components/views/donate/RecurringDonationCard.tsx (3)

57-58: Imported GIVBackToast and usePurpleList to support new functionality.

---

171-172: Introduced variables to check GIVBack eligibility and purple list status.

---

912-918: Styled GIVBackToast to ensure it fits the design requirements.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (2)

src/components/views/donate/CryptoDonation.tsx (1)

Line range hint 93-93: Several instances of non-null assertions and any types detected. These can lead to runtime errors if not handled properly.

Consider replacing any with more specific types and handling potential null values gracefully to improve type safety and predictability of the code.

Also applies to: 96-96, 101-101, 122-122, 184-184, 186-186, 192-192, 193-193, 289-289, 300-300, 464-464

src/components/views/donate/RecurringDonationCard.tsx (1)

Line range hint 235-235: Using target="_blank" without rel="noreferrer" can be a security risk.

Consider adding rel="noreferrer" to the anchor tag to prevent potential security vulnerabilities.

- <a href='https://www.superfluid.finance/' target='_blank'>
+ <a href='https://www.superfluid.finance/' target='_blank' rel='noreferrer'>

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1d4aa5d and 8222746.

Files selected for processing (3)

• src/components/views/donate/CryptoDonation.tsx (3 hunks)
• src/components/views/donate/GIVBackToast.tsx (2 hunks)
• src/components/views/donate/RecurringDonationCard.tsx (5 hunks)

Additional Context Used

Biome (28)

src/components/views/donate/CryptoDonation.tsx (20)

93-93: Forbidden non-null assertion.

---

96-96: Unexpected any. Specify a different type.

---

101-101: Unexpected any. Specify a different type.

---

122-122: Unexpected any. Specify a different type.

---

141-150: Prefer for...of instead of forEach.

---

179-196: Prefer for...of instead of forEach.

---

184-184: Forbidden non-null assertion.

---

186-186: Forbidden non-null assertion.

---

192-192: Forbidden non-null assertion.

---

193-193: Forbidden non-null assertion.

---

247-249: This else clause can be omitted because previous branches break early.

---

269-269: Use === instead of ==.
== is only allowed when comparing against null

---

289-289: Forbidden non-null assertion.

---

300-300: Forbidden non-null assertion.

---

464-464: Forbidden non-null assertion.

---

508-508: Template literals are preferred over string concatenation.

---

1-2: Some named imports are only used as types.

---

12-13: Some named imports are only used as types.

---

39-43: All these imports are only used as types.

---

61-62: All these imports are only used as types.

src/components/views/donate/GIVBackToast.tsx (1)

17-18: Declare variables separately

src/components/views/donate/RecurringDonationCard.tsx (7)

69-71: This else clause can be omitted because previous branches break early.

---

84-86: This else clause can be omitted because previous branches break early.

---

91-91: Forbidden non-null assertion.

---

235-235: Avoid using target="_blank" without rel="noreferrer".

---

385-385: Unexpected any. Specify a different type.

---

751-751: Forbidden non-null assertion.

---

42-43: All these imports are only used as types.

Additional comments not posted (5)

src/components/views/donate/GIVBackToast.tsx (2)

12-12: Added className prop to enhance styling flexibility.

---

48-48: Properly applied the className prop to the ToastContainer. This ensures that the styling can be customized externally as needed.

src/components/views/donate/RecurringDonationCard.tsx (3)

57-57: Imported GIVBackToast for use in the component. This aligns with the PR's objective to integrate the givback toast into recurring donations.

---

170-170: Correctly determined the project's eligibility for GIVBack based on its verified status.

---

909-915: Styled the GIVBackToast component to fit the design requirements of the recurring donation card.