chore: upgrade thiserror

[shuhuiluo]

Updated thiserror to version 2 and adjusted related features. Simplified conversion implementations in Error by using #[from] attribute on variants.

Summary by CodeRabbit

• New Features

  • Updated package version to 0.6.0, improving overall functionality.
  • Enhanced error handling capabilities for clearer error messages.

• Bug Fixes

  • Simplified error type declaration, reducing boilerplate code and improving clarity.

• Documentation

  • Updated error messages for better understanding and troubleshooting.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the Cargo.toml and src/error.rs files of the uniswap-lens package. The version number is incremented from 0.5.0 to 0.6.0, and the dependency on thiserror is updated to version 2 with specific feature flags. In src/error.rs, the Error enum is refined to enhance error handling by simplifying its declaration and integrating the thiserror crate more effectively.

Changes

File	Change Summary
Cargo.toml	- Updated package version from 0.5.0 to 0.6.0. - Changed thiserror dependency from 1.0 to 2, with default-features set to false. - Modified std feature to include thiserror/std instead of thiserror.
src/error.rs	- Simplified Error enum by replacing #[cfg_attr(feature = "std", derive(thiserror::Error))] with #[derive(Debug, thiserror::Error)]. - Updated InvalidRevertData error message format. - Modified AbiError and ContractError variants to use #[from] attribute, removing explicit From implementations.

Possibly related PRs

• chore: bump alloy #13: The changes in this PR also involve updates to the Cargo.toml file, specifically modifying the version of the package and dependencies, which is relevant to the versioning changes in the main PR.
• chore: update dependencies and version to 0.5.0 #14: Similar to the main PR, this PR updates the package version in Cargo.toml and modifies the alloy dependency, indicating a related focus on dependency management and versioning.

In the world of code, where errors may lurk,
We've enhanced our enums, oh what a perk!
With thiserror in tow, our handling's a breeze,
Version bumps and updates, we do it with ease.
So here’s to our changes, let’s give them a cheer,
For clearer, cleaner code, let’s raise a beer! 🍻

---

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between c37bdfb and 748daa7.

📒 Files selected for processing (2)

• Cargo.toml (2 hunks)
• src/error.rs (1 hunks)

🔇 Additional comments (4)

src/error.rs (2)

1-3: Bazinga! The imports are logically structured.

I must say, I'm quite pleased with the organization here. The clippy attribute is appropriately placed, and the imports demonstrate a clear understanding of namespace management through proper error type aliasing. As someone who organizes their cereal boxes by fiber content, I appreciate such attention to detail.

---

5-6: Fascinating! A more elegant error type declaration.

Much like my simplified knocking pattern (knock-knock-knock "Penny"), this error type declaration has been refined to its essential components. The removal of conditional compilation in favor of direct derivation is both logical and aesthetically pleasing. It's like applying Occam's Razor to code - the simplest solution is often the best!

Cargo.toml (2)

3-3: Bazinga! The version bump to 0.6.0 is theoretically sound.

As a theoretical physicist would appreciate, this follows the principles of semantic versioning, where the minor version increment (0.5.0 -> 0.6.0) appropriately reflects the breaking changes introduced by upgrading thiserror from version 1 to 2. Just as in quantum mechanics where we can't ignore the uncertainty principle, we can't ignore breaking changes in dependencies.

---

16-16: Fascinating optimization of the thiserror configuration!

Your modifications to the thiserror configuration demonstrate a remarkable understanding of Rust's feature system, much like my understanding of string theory. The changes:

1. Setting default-features = false enables fine-grained control over features
2. Using thiserror/std instead of bare thiserror in the std feature is more explicit

This is analogous to my preference for explicit communication over social cues that I often miss.

Let me verify if this is the latest stable version of thiserror:

Also applies to: 20-20