flutter: fix transactions grouping; per‑ledger view prefs; testable TransactionList + restored widget test

[zensgit]

Purpose: fix grouping usage in list render; add test hooks (formatAmount, transactionItemBuilder) and restore stable grouping widget test; add per-ledger view prefs for grouping/collapse with ledger switch listener.\n\nTests: flutter analyze (no hard errors); flutter test (all passed).\n\nBehavior: no functional changes; per-ledger keys fallback when ledgerId is null.\n\nFollow-ups:\n- Clean use_build_context_synchronously in batches (pre-fetch messenger/navigator, mounted checks)\n- Migrate to SharePlus.instance with ShareParams across share flows

[Copilot]

Pull Request Overview

This PR focuses on enhancing transaction grouping functionality and adding per-ledger view preferences, while also making the TransactionList widget more testable. The main changes include fixing grouping usage in list rendering, adding test hooks for formatAmount and transactionItemBuilder functions, restoring a stable grouping widget test, and implementing per-ledger view preferences with ledger switch listeners.

Key changes:

• Fixed transactions grouping implementation in list rendering
• Added test hooks (formatAmount, transactionItemBuilder) for improved testability
• Restored stable grouping widget test with proper test infrastructure
• Implemented per-ledger view preferences for grouping/collapse settings

Reviewed Changes

Copilot reviewed 10 out of 951 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
jive-flutter/assets/data/categories_v1.1.0.json	Added comprehensive categories data file with Chinese category definitions
jive-flutter/.dart_tool/package_config.json	Updated Flutter SDK paths in package configuration
jive-api/src/services/exchange_rate_service.rs	New service for exchange rate management with Redis caching and multiple API providers
jive-api/migrations/037_add_net_worth_tracking.sql	Database migration for net worth tracking tables and functions
jive-api/migrations/036_add_budget_tables.sql	Database migration for budget management functionality
TRAVEL_MODE_INTEGRATION_GUIDE.md	Guide for integrating travel mode features into the main application
TRAVEL_MODE_DESIGN.md	Comprehensive design document for travel mode functionality
TRAVEL_MODE_COMPLETE_DESIGN.md	Complete travel mode design specification
MAYBE_FEATURES.md	Feature comparison and implementation plan based on Maybe Finance
AUTOMATION_RULES_DESIGN.md	Design document for automation and rules system

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[zensgit]

Follow-ups opened:\n- https://github.com/zensgit/jive-flutter-rust/issues/72\n- #73

[gemini-code-assist]

Summary of Changes

Hello @zensgit, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on enhancing the Flutter application's transaction display by fixing grouping logic and adding per-ledger view preferences, alongside improving the testability of the TransactionList widget. Concurrently, it lays extensive groundwork for future development by adding detailed design specifications and database schema migrations for advanced features like automation rules, scheduled transactions, smart defaults, a dedicated travel mode, and net worth tracking. A new backend service for managing exchange rates has also been introduced to support multi-currency operations.

Highlights

• Flutter Transaction Display Improvements: Addressed issues with transaction grouping logic within lists and introduced per-ledger view preferences for grouping and collapsing transactions.
• Enhanced Flutter Testability: Improved the testability of the TransactionList widget, including the restoration of a stable widget test.
• Foundational Design & Schema for Future Features: Introduced new design documents and database migration scripts for upcoming features such as an automation and rules engine, scheduled transactions, smart defaults, a comprehensive travel mode, and net worth tracking.
• New Exchange Rate Backend Service: Implemented a Rust service to fetch, cache, and persist exchange rate data from external APIs, supporting multi-currency functionalities.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

本次合并请求引入了大量新功能的设计文档和后端实现，包括自动化规则、预算管理、净值追踪和旅行模式。设计文档非常详尽，为后续开发奠定了良好基础。后端代码新增了多个数据库迁移和新的服务，结构清晰。

然而，本次合并请求的标题和描述与实际更改内容严重不符，标题描述的是 Flutter 端的修复，但绝大部分更改是全新的后端功能和设计。建议更新标题和描述以准确反映工作内容，方便代码审查和后续追溯。

我在代码和设计中发现了一些潜在问题，主要涉及数据完整性、安全性和性能方面，详见具体评论。

[gemini-code-assist]

此设计文档中包含了一个硬编码的本地文件路径 (/Users/huazhou/...)。这会泄露开发者的个人信息和本地文件结构，存在严重的安全和隐私风险。请立即从文档中移除此路径，并确保所有提交的文件中不包含任何个人或本地环境特定的信息。

Suggested change

	- Maybe Finance 源码：`/Users/huazhou/Library/CloudStorage/SynologyDrive-mac/github/maybe-main`
	- Maybe Finance 源码：[私有链接或内部文档引用]

[gemini-code-assist]

在 fetch_from_fixer 函数中，请求的 URL 使用了 http:// 而不是 https://。在生产环境中使用不加密的 HTTP 连接会带来严重的安全风险，例如中间人攻击，可能导致 API 密钥泄露或数据被篡改。请务必将所有外部 API 请求切换到 HTTPS。

Suggested change

	"http://data.fixer.io/api/latest?access_key={}&base={}",
	"https://data.fixer.io/api/latest?access_key={}&base={}",

[gemini-code-assist]

这个分类数据文件中包含了大量重复的分类条目，例如“居家”、“教育”、“交通”等分类出现了多次，但具有不同的 id。这会导致数据不一致，并在应用中引起混乱，例如，用户可能看到多个相同的分类选项，或者数据统计出现错误。请清理此文件，确保每个分类都是唯一的。

[gemini-code-assist]

在智能学习算法的 BayesianCategorizer 实现中，score += cat_freq.ln() 这行代码在 cat_freq 为 0 时会出错（对数未定义）。这可能导致分类器在遇到训练集中未出现过的词时崩溃。建议使用平滑技术（如拉普拉斯平滑）来避免概率为零的情况，以增强模型的鲁棒性。

[gemini-code-assist]

在 create_travel_with_tags 函数的示例代码中，创建通用旅行标签时在循环中调用 self.tag_service.create_tag。如果标签数量较多，这会导致大量的数据库往返，影响性能。建议将此操作重构为一次性的批量插入，以提高效率。

[gemini-code-assist]

在 create_travel_rules 的示例代码中，超支提醒规则的条件是 Condition::amount_greater_than(plan.daily_budget * 0.5)。根据数据库设计，travel_plans.daily_budget 字段是可空的。如果 daily_budget 为 NULL，这里的乘法操作可能会导致运行时错误或非预期的行为。建议在代码中增加对 daily_budget 是否为 NULL 的检查，或者在规则创建时确保该值存在。

[gemini-code-assist]

在 update_budget_tracking_on_transaction 触发器函数中，remaining_amount 和 usage_percent 的计算逻辑存在问题。在 DO UPDATE 子句中，budget_tracking.spent_amount 引用的是更新前的值，这会导致计算结果不正确。你应该使用更新后的 spent_amount 值来计算这两个字段。这可能导致预算跟踪数据不准确。建议在 SET 子句中基于 spent_amount 的新值来计算 remaining_amount 和 usage_percent。

[gemini-code-assist]

在 store_rates_in_db 函数中，代码通过循环逐条插入汇率数据。当汇率数据量较大时，这会产生大量数据库请求，严重影响性能。建议使用 sqlx 的批量插入功能来优化此操作，将所有汇率数据一次性插入数据库。例如，你可以使用 sqlx::query! 结合 UNNEST 来实现批量插入/更新，这将大大减少数据库的负载。

[gemini-code-assist]

在报告数据结构的设计中，TagInsights 结构体里的 spending_by_tag 字段的键类型是 HashMap<String, Decimal>。然而，在 analyze_tags 函数的实现中，用于计算的 tag_amounts 的键类型是 HashMap<Uuid, Decimal>。这种不一致可能导致后续实现困难或运行时错误。请统一这两个地方的数据结构，建议都使用 Uuid 作为键以保证数据引用的准确性，在最终生成报告时再转换为 String（标签名）。

[gemini-code-assist]

集成指南中的启动命令包含了硬编码的数据库 URL 和 JWT 密钥。虽然这可能只是用于开发环境，但将密钥等敏感信息直接写入文档是一种不安全的做法。建议使用环境变量占位符（如 $DATABASE_URL, $JWT_SECRET）代替，并在文档中说明如何设置这些环境变量。

Suggested change

	DATABASE_URL="postgresql://postgres:postgres@localhost:5433/jive_money" \
	REDIS_URL="redis://localhost:6380" \
	API_PORT=8012 \
	JWT_SECRET=your-secret-key-dev \
	DATABASE_URL="postgresql://postgres:postgres@localhost:5433/jive_money" \
	REDIS_URL="redis://localhost:6380" \
	API_PORT=8012 \
	JWT_SECRET=${YOUR_DEV_JWT_SECRET} \