合并更改

[TC999]

dev-->main

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced logging capabilities with the introduction of a logging utility.
  • Users can now enable or disable logging through a checkbox in the UI.
  • The application now supports scanning different application data folders ("Roaming", "Local", "LocalLow").

• Bug Fixes

  • Improved error handling and logging for folder deletion and scanning processes.

• Documentation

  • Updated logging messages to support localization in Chinese.

• Chores

  • Added .log files to .gitignore to prevent tracking of log files.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve several updates to enhance logging capabilities and error handling in the AppDataCleaner application. Key modifications include the addition of logging dependencies in Cargo.toml, the introduction of a new logging utility in src/logger.rs, and updates to various functions to integrate logging. The .gitignore file has been modified to exclude log files, and the user interface has been adjusted to allow users to enable or disable logging and select application data folders.

Changes

File	Change Summary
.gitignore	Added entry *.log to ignore log files; added newline at the end.
Cargo.toml	Added dependencies: log = "0.4" and simplelog = "0.12".
src/delete.rs	Updated delete_folder function with logging and error handling; localized error messages in Chinese.
src/logger.rs	Introduced logging utility with functions: init_logger, log_info, and log_error.
src/main.rs	Imported logger module; initialized logging in main function and added startup log message.
src/scanner.rs	Modified scan_appdata to accept folder_type; improved error handling and scanning logic.
src/ui.rs	Updated AppDataCleaner struct with new fields; modified update method for logging and UI enhancements.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant UI
    participant Logger
    participant Scanner

    User->>UI: Select folder type
    UI->>Logger: Check if logging enabled
    alt Logging enabled
        UI->>Logger: Log "Scanning started"
    end
    UI->>Scanner: Start scanning process
    Scanner->>Logger: Log "Scanning folder"
    Scanner-->>UI: Return scan results
    UI->>Logger: Log "Scan completed"

Loading

🐰 "In the code, a change so bright,
Log files ignored, a cleaner sight.
With logging now, we track with ease,
Errors caught like autumn leaves.
AppDataCleaner hops with glee,
In every log, a tale to see!" 🐇

---

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>, 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 resolve resolve all the CodeRabbit review comments.
• @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.