fix: update notification view image on setup flow

[kushagrasarathe]

• updated notification view image to thinking peanut in setup flow
  fixes TASK-8270

Summary by CodeRabbit

• New Features

  • Added a new PEANUTMAN_THINKING asset to the project

• Style

  • Updated image styling for notification permission step, adjusting image size and margin

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
peanut-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 24, 2025 7:58am

[coderabbitai]

Walkthrough

This pull request introduces a new SVG asset for the PEANUTMAN character by adding an export statement in the src/assets/peanut/index.ts file. Correspondingly, the Setup.consts.tsx file has been updated to use this new asset, replacing the previous notificationPeanut with PEANUTMAN_THINKING. The changes modify the image source and adjust the image styling for the notification permission step.

Changes

File	Change Summary
src/assets/peanut/index.ts	Added new export for PEANUTMAN_THINKING SVG asset
src/components/Setup/Setup.consts.tsx	- Removed notificationPeanut import - Added PEANUTMAN_THINKING import - Updated notification step image source - Modified image styling (width and margin)

Possibly related PRs

• [TASK-8044] fix: temporarily remove initial view from send flow #605: Direct connection with the PEANUTMAN_THINKING constant addition
• Updated background preview image TASK-7883 #622: Similar asset export pattern in src/assets/social-previews/index.ts

Suggested reviewers

• Hugo0

Poem

🥜 A Peanut's Thinking Pose 🤔

In pixels bright, a new asset arrives,
PEANUTMAN ponders, his spirit thrives,
From setup screen to import's embrace,
A thinking image with whimsical grace!

🐰✨ Hop, hop, hooray! 🎉

---

📜 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 66fee2d and f4edd5d.

⛔ Files ignored due to path filters (1)

• src/assets/peanut/peanutman-thinking.svg is excluded by !**/*.svg

📒 Files selected for processing (2)

• src/assets/peanut/index.ts (1 hunks)
• src/components/Setup/Setup.consts.tsx (2 hunks)

🔇 Additional comments (4)

src/assets/peanut/index.ts (1)

9-9: Consistent naming across exported assets.
All PEANUTMAN assets follow an uppercase naming scheme with underscores, and introducing PEANUTMAN_THINKING aligns well with the established pattern.

src/components/Setup/Setup.consts.tsx (3)

64-64: Image source updated to PEANUTMAN_THINKING.
This change fulfills the PR objective of using the new thinking peanut asset and looks good.

---

68-68: Slightly reduced image width for improved layout.
The updated class sets a smaller width and adjusts margins, which may enhance the overall layout on smaller screens.

---

4-4: Remove any lingering references to the old notificationPeanut.
This import line indicates the project is now consistently using PEANUTMAN_THINKING. Please verify that no unused references to notificationPeanut remain in the codebase.

✅ Verification successful

No lingering references to notificationPeanut found ✅
The codebase has been fully migrated to use the new PEANUTMAN_* naming convention consistently.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any references to the old notificationPeanut import.
rg "notificationPeanut"

Length of output: 23

---

Script:

#!/bin/bash
# Search for variations of notification and peanut references
echo "=== Searching for notification-peanut variations ==="
rg -i "notification.*peanut|peanut.*notification"

echo -e "\n=== Checking for peanut-related image assets ==="
fd -e png -e svg -e jpg -e jpeg -e gif | grep -i "peanut"

echo -e "\n=== Checking asset imports ==="
rg "from.*assets.*peanut" -g "*.{ts,tsx,js,jsx}"

Length of output: 1575

✨ 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.

[notion-workspace]

replace 1.3 asset to thinking anim