fix: error message check for polling

[sstefdev]

• changed the message in the if statement in the catch block

Testing

I tested by throwing an Error, couldn't reproduce it, I did it like this

And this is how the modal looks:

Summary by CodeRabbit

• Bug Fixes
  • Improved error handling in the invoice creation process to provide more accurate feedback for transaction confirmation issues. Users will now receive specific notifications if a transaction confirmation fails.

[coderabbitai]

Walkthrough

The recent changes enhance the error handling logic in the create-invoice-form.svelte file. By refining the error detection from a general timeout message to a specific failure regarding transaction confirmation, the code now provides more accurate feedback. This improvement enables developers to better diagnose issues and enhances the overall user experience during transaction processing.

Changes

Files	Change Summary
packages/create-invoice-form/src/lib/create-invoice-form.svelte	Updated error handling to focus on "Transaction confirmation not received" instead of a generic timeout error.

---

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.
  • @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 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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between f99fe6e and 56a85c7.

Files selected for processing (1)

• packages/create-invoice-form/src/lib/create-invoice-form.svelte (1 hunks)

[coderabbitai]

Fix the typographical error in the error message.

The error message contains a typographical error: "Transactioon" should be "Transaction".

- if (error.message.includes("Transactioon confirmation not received")) {
+ if (error.message.includes("Transaction confirmation not received")) {

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	if (error.message.includes("Transactioon confirmation not received")) {
	if (error.message.includes("Transaction confirmation not received")) {