fix: added payment check when invoice is paid

[sstefdev]

Fixes #40

• added a boolean for the dashboard to check if the request is paid
• added fetching new request when is paid

Summary by CodeRabbit

• New Features
  • Introduced a new status indicator to show if an invoice request has been paid.
  • Added functionality to fetch and update individual request data more efficiently.

[coderabbitai]

Walkthrough

The changes introduce a new isRequestPayed variable to track the payment status of requests in the Invoice Dashboard. This variable is exported and utilized within the invoice-view.svelte and view-requests.svelte components. Additionally, a new function getOneRequest is implemented to fetch and update request data, ensuring that the status column updates accurately after a payment is made without requiring a page refresh.

Changes

Files	Change Summary
packages/invoice-dashboard/src/lib/dashboard/invoice-view.svelte	Added an exported variable isRequestPayed of type boolean to indicate if a request has been paid.
packages/invoice-dashboard/src/lib/view-requests.svelte	Introduced isRequestPayed variable, implemented getOneRequest function, and updated logic for request handling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant InvoiceDashboard
    participant InvoiceView
    participant Backend
    
    User->>InvoiceDashboard: Make Payment
    InvoiceDashboard->>Backend: Process Payment
    Backend-->>InvoiceDashboard: Payment Success
    InvoiceDashboard->>InvoiceView: Update isRequestPayed
    InvoiceDashboard->>Backend: getOneRequest
    Backend-->>InvoiceDashboard: Request Data
    InvoiceDashboard->>InvoiceView: Bind isRequestPayed
    InvoiceView-->>User: Display Updated Status

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Status column updates to "Paid" after making a payment (#40)	✅

---

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 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: ASSERTIVE

Commits

Files that changed from the base of the PR and between 37f3d67 and fa51c63.

Files selected for processing (2)

• packages/invoice-dashboard/src/lib/dashboard/invoice-view.svelte (2 hunks)
• packages/invoice-dashboard/src/lib/view-requests.svelte (3 hunks)

Additional comments not posted (4)

packages/invoice-dashboard/src/lib/dashboard/invoice-view.svelte (2)

36-36: LGTM!

The introduction of the isRequestPayed variable is straightforward and aligns with the PR objectives.

---

144-144: LGTM!

Setting isRequestPayed to true upon payment confirmation ensures accurate state management.

packages/invoice-dashboard/src/lib/view-requests.svelte (2)

49-49: LGTM!

The initialization of the isRequestPayed variable to false is straightforward and aligns with the PR objectives.

---

477-477: LGTM!

Binding isRequestPayed to the InvoiceView component ensures accurate state management.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits

Files that changed from the base of the PR and between fa51c63 and cc2e8ee.

Files selected for processing (1)

• packages/invoice-dashboard/src/lib/view-requests.svelte (4 hunks)

Additional comments not posted (3)

packages/invoice-dashboard/src/lib/view-requests.svelte (3)

49-49: Introduction of isRequestPayed variable is appropriate.

The new boolean variable isRequestPayed is introduced to track the payment status of a request. This aligns with the PR objectives and seems necessary for the functionality.

---

71-72: Reactive statement to call getOneRequest is appropriate.

The reactive statement ensures that the request data is refreshed whenever the payment status changes. This aligns with the PR objectives to update the status column without needing a page refresh.

---

96-116: getOneRequest function implementation is appropriate.

The function fetches and updates the request data based on the activeRequest. Error handling is included, and the loading state is managed appropriately.