fix: error thrown when logo not set

[aimensahnoun]

• There was an issue where it would throw an error because there was no logo passed.

Summary by CodeRabbit

• New Features

  • Improved handling of the seller logo in the payment widget, ensuring robustness by providing a default value if the logo is undefined.

• Bug Fixes

  • Enhanced error prevention related to undefined values for the seller logo.

• Chores

  • Updated version number of the payment widget package and various development dependencies to their latest versions.

[coderabbitai]

Walkthrough

The pull request includes updates to the package.json file for the @requestnetwork/payment-widget package, incrementing the version from 0.3.1 to 0.3.2 and modifying the dependency version for @requestnetwork/request-client.js from ^0.49.1-next.2088 to ^0.50.0. Additionally, the payment-widget.svelte component has been updated to enhance the handling of the sellerLogo property, ensuring it defaults to an empty string if undefined. The overall structure and logic of the component remain unchanged.

Changes

File	Change Summary
packages/payment-widget/package.json	- Version updated from 0.3.1 to 0.3.2. - Updated dependency: - @requestnetwork/request-client.js from ^0.49.1-next.2088 to ^0.50.0.
packages/payment-widget/src/lib/payment-widget.svelte	- Modified sellerLogo handling in PaymentComplete component to use `sellerInfo?.logo

Possibly related PRs

• feat: add billing information support #123: The changes in this PR enhance the payment widget by adding support for buyerInfo, which is directly related to the handling of buyer information in the main PR.
• fix: initial buyerInfo not registered correctly #124: This PR modifies the currentBuyerInfo variable in payment-widget.svelte, which is relevant to the changes made in the main PR regarding buyer information handling.
• chore: increase payment-widget version #145: This PR updates the version of the @requestnetwork/payment-widget, which is consistent with the version increment in the main PR.
• feat: improve UI of payment-widget #182: This PR introduces changes to the payment-widget.svelte component, which may relate to the overall functionality and user interface improvements in the main PR.
• chore: upgrade sdk version #187: Similar to chore: increase payment-widget version #145, this PR also updates the version of the @requestnetwork/payment-widget, aligning with the version changes in the main PR.

Suggested reviewers

• MantisClone
• sstefdev
• rodrigopavezi

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8bca5cd and f9e2522.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• packages/payment-widget/package.json (2 hunks)

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

• packages/payment-widget/package.json

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

packages/payment-widget/src/lib/payment-widget.svelte (1)

271-271: LGTM! The fix properly handles undefined logo.

The change correctly implements null-safe access to sellerInfo.logo with a fallback to empty string, preventing errors when the logo is not set.

Consider updating the SellerInfo type to make the logo property explicitly optional:

interface SellerInfo {
  logo?: string;
  // ... other properties
}

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 10fab8b and 8bca5cd.

📒 Files selected for processing (2)

• packages/payment-widget/package.json (1 hunks)
• packages/payment-widget/src/lib/payment-widget.svelte (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• packages/payment-widget/package.json