chore: fix crashing issues - add encryption status handling and improve transaction parameter handling

[rodrigopavezi]

Changes

• Bump version to 0.3.2
• add encryption status handling and improve transaction parameter handling

Summary by CodeRabbit

• New Features
  • Transactions now display an "Encrypted" status along with additional encryption details, enhancing clarity for secure exchanges.
  • Payment details have been refined to improve accuracy in displaying expected amounts.
• Chores
  • Updated the package version to 0.3.2 for improved consistency and release management.

[coderabbitai]

Walkthrough

This change set updates the package version and extends transaction handling to support encryption details. The version number in the package manifest has been bumped. In the request page, a new optional prop (isEncrypted) has been added to conditionally render encryption status, and transaction data is now handled more safely using optional chaining with parameters split into two variables. In addition, the Transaction type has been extended with new optional encryption-related fields and utility methods have been updated to access data safely.

Changes

File(s)	Change Summary
package.json	Updated version number from "0.3.1" to "0.3.2".
src/.../page.tsx	- Added an optional isEncrypted prop to ActorInfoSection. - Split transaction parameters into createParametersFromFirstTransaction and createParametersFromLastTransaction. - Updated logic to safely access transaction data using optional chaining and adjusted rendering to include an encryption status row.
src/.../types.ts & src/.../utils.ts	- Extended the Transaction interface with four new optional properties: encryptedData, encryptedKeys, encryptionMethod, and publicKeys. - Modified utility functions to access extensionsData using optional chaining, enhancing the robustness of data retrieval.

Sequence Diagram(s)

sequenceDiagram
  participant R as RequestPage
  participant T as TransactionData
  participant A as ActorInfoSection

  R->>T: Fetch first and last transaction parameters safely
  T-->>R: Return transaction parameters (with optional encryption details)
  R->>A: Pass actor info and isEncrypted flag
  alt if isEncrypted is true
    A->>R: Render encryption status row
  else
    A-->>R: Render standard transaction info
  end

Loading

Possibly related PRs

• chore: increase version for request scan release #67: Involves a version update to package.json, similar to the current version bump.
• Chore/bump version #82: Contains changes related to updating the version number in package.json, indicating a direct relationship at the code level.

Suggested reviewers

• aimensahnoun
• sstefdev

---

📜 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 0c80dea and 88ae5c6.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (4)

• package.json (1 hunks)
• src/app/request/[id]/page.tsx (8 hunks)
• src/lib/types.ts (1 hunks)
• src/lib/utils.ts (2 hunks)

🧰 Additional context used

🧬 Code Definitions (1)

src/app/request/[id]/page.tsx (1)

src/lib/utils.ts (4)

• getTransactionCreateParameters (154-159)
• getContentDataFromCreateTransaction (161-170)
• getPaymentDataFromCreateTransaction (172-177)
• getAmountWithCurrencySymbol (46-58)

🔇 Additional comments (15)

package.json (1)

3-3: Version bump aligned with added encryption capabilities

The version has been incremented from 0.3.1 to 0.3.2, which corresponds with the encryption handling features and transaction parameter improvements mentioned in the PR description.

src/lib/types.ts (1)

32-35: Good addition of encryption-related fields to the Transaction interface

These new optional fields provide the necessary structure to support encryption capabilities in the application, which aligns with the PR objective of handling encryption status. The fields are properly marked as optional which maintains backward compatibility.

src/lib/utils.ts (2)

164-164: Good improvement with optional chaining

Using optional chaining here makes the code more resilient against potential undefined or null values, which helps prevent runtime errors.

---

175-176: Safer parameter handling with optional chaining

The implementation now safely accesses potentially undefined properties using optional chaining throughout, which makes the code more robust and prevents potential crashes when handling transaction data.

src/app/request/[id]/page.tsx (11)

55-58: Good enhancement to support encryption status display

The component signature has been updated to accept an isEncrypted flag, which allows for conditional rendering based on encryption status. This change aligns well with the new transaction properties.

---

68-79: Well-implemented conditional rendering for encrypted content

This new conditional rendering logic provides a user-friendly indication when data is encrypted, improving the user experience by clearly communicating the encryption status.

---

190-193: Good refactoring of transaction parameters

Splitting the transaction parameters into separate variables improves code readability and makes the intentions clearer by distinguishing between parameters from the first and last transactions.

---

195-200: Improved data handling with more specific parameter access

The code now correctly uses the appropriate transaction parameters for content and payment data, making the intent clearer and the code more maintainable.

---

211-211: Safe access with optional chaining in status check

Using optional chaining for accessing the expected amount prevents potential runtime errors and improves the robustness of the application.

---

227-231: Consistent parameter usage in PDF export

The PDF export function now consistently uses the first transaction's parameters, making the code more predictable and maintainable.

---

304-307: Enhanced payee details with encryption status

Passing the encryption status to the ActorInfoSection component improves the user experience by showing appropriate information based on whether the data is encrypted.

---

325-328: Enhanced payer details with encryption status

Similar to the payee details, this change improves the user experience by consistently displaying the encryption status for payer information.

---

335-340: Safe parameter access with optional chaining

The code now safely accesses potentially undefined transaction parameters, preventing potential runtime errors and making the application more robust.

---

385-392: Helpful addition of encryption status display

Adding an explicit row for encryption status improves the user experience by clearly communicating whether the transaction data is encrypted or not.

---

396-414: Well-implemented conditional rendering for raw content data

This change provides appropriate handling for both encrypted and non-encrypted content, improving the user experience by showing relevant information based on the encryption status.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.