fix: pad info should be removed after being used

[Kilerd]

Summary by CodeRabbit

• New Features

  • Introduced functionality for financial transactions and balance computations in CNY.
  • Added a set of validations for the /api/store endpoint to check response data conditions.

• Bug Fixes

  • Improved the logic for retrieving and handling pad account information in the Beancount data type.

• Chores

  • Updated the latestmap dependency version from 0.1 to 0.2.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Recent updates enhance the Beancount extension by upgrading the latestmap dependency from version 0.1 to 0.2. This change improves the functionality for handling pad account information in the Beancount data type. Additionally, new files for integration tests have been introduced to validate financial transactions involving account balances in the CNY currency.

Changes

Files	Change Summary
extensions/beancount/Cargo.toml	Updated latestmap dependency version from 0.1 to 0.2.
extensions/beancount/src/lib.rs	Modified logic for pad account information in Beancount implementation using new methods.
integration-tests/2/main.bean	Added financial transaction and balance computation commands for CNY currency tests.
integration-tests/2/validations.json	Introduced validations for /api/store endpoint responses focusing on error and transaction flags.

Sequence Diagram(s)

Poem

In Beancount's code, a change was made,
New logic blooms, old flaws will fade. 🌱
Accounts and balances now so bright,
With latestmap's new guiding light. ✨
Transactions clear, in CNY tide,
Beancount strides with metrics wide.
A rabbit cheers this fresh update,
Hopping in joy, a coder’s mate! 🐇💻

---

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.

[Kilerd]

@coderabbitai review

[coderabbitai]

Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1f3f940 and 6a037c5.

Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

Files selected for processing (4)

• extensions/beancount/Cargo.toml (1 hunks)
• extensions/beancount/src/lib.rs (1 hunks)
• integration-tests/2/main.bean (1 hunks)
• integration-tests/2/validations.json (1 hunks)

Files not reviewed due to errors (1)

• extensions/beancount/src/lib.rs (no review received)

Files skipped from review due to trivial changes (2)

• extensions/beancount/Cargo.toml
• integration-tests/2/validations.json

Additional comments not posted (4)

integration-tests/2/main.bean (4)

1-1: LGTM! The declaration of the commodity "CNY" is essential for the subsequent transactions.

---

3-4: LGTM! Opening the accounts correctly sets up the necessary structure for the financial records.

---

6-6: The pad directive is correctly used to align the balance of "Assets:A" with "Equity:OpenBalance".

---

8-9: Ensure these balance entries are tested to verify that they reflect the expected state of the accounts after transactions.