chore: fix lint

[devhaozi]

📑 Description

Summary by CodeRabbit

• Chores
  • Updated module dependencies, adding new ones and removing outdated or unnecessary ones. This helps improve overall stability, performance, and security of the application. No direct impact on end-user functionality.

Closes https://github.com/goravel/goravel/issues/?

✅ Checks

• Added test cases for my code

[coderabbitai]

Walkthrough

This update to the go.mod file primarily involves significant changes to module dependencies, featuring the addition and removal of numerous indirect dependencies. Key modules added include filippo.io/edwards25519, github.com/atotto/clipboard, among others. Conversely, many dependencies, such as go.opentelemetry.io/otel and related packages, have been removed, underscoring a substantial revision in the dependency landscape.

Changes

Files or Group of Files	Change Summary
go.mod	Added new dependencies: filippo.io/edwards25519, github.com/atotto/clipboard, and others.
go.mod	Removed dependencies: go.opentelemetry.io/otel, github.com/charmbracelet/bubbles, and others.

Poem

In the realm of Go where coders play,
Dependencies come and go, sway by sway,
Edwards and clipboard now in the dance,
Opentelemetry bows, exits the trance.
Modules shift in this binary ballet,
Celebrate the clean slate, hip-hip hooray!

Tip

AI model upgrade

gpt-4o model for reviews and chat is now live

OpenAI claims that this model is better at understanding and generating code than the previous models. Please join our Discord Community to provide any feedback or to report any issues.

---

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.

[devhaozi]

@coderabbitai summary

[coderabbitai]

Actions performed

Summary regeneration triggered.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.92%. Comparing base (d288c4c) to head (2143f61).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #536   +/-   ##
=======================================
  Coverage   69.92%   69.92%           
=======================================
  Files         180      180           
  Lines       11049    11049           
=======================================
  Hits         7726     7726           
  Misses       2751     2751           
  Partials      572      572           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[devhaozi]

@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 d288c4c and 2143f61.

Files selected for processing (1)

• go.mod (4 hunks)

Additional comments not posted (28)

go.mod (28)

57-57: Verify the necessity of filippo.io/edwards25519 dependency.

Ensure that the filippo.io/edwards25519 dependency is required for the project and there are no alternatives that might be more suitable.

---

64-64: Verify the necessity of github.com/atotto/clipboard dependency.

Ensure that the github.com/atotto/clipboard dependency is required for the project and there are no alternatives that might be more suitable.

---

66-66: Verify the necessity of github.com/aymanbagabas/go-osc52/v2 dependency.

Ensure that the github.com/aymanbagabas/go-osc52/v2 dependency is required for the project and there are no alternatives that might be more suitable.

---

67-67: Verify the necessity of github.com/catppuccin/go dependency.

Ensure that the github.com/catppuccin/go dependency is required for the project and there are no alternatives that might be more suitable.

---

69-69: Verify the necessity of github.com/charmbracelet/bubbles dependency.

Ensure that the github.com/charmbracelet/bubbles dependency is required for the project and there are no alternatives that might be more suitable.

---

70-70: Verify the necessity of github.com/charmbracelet/bubbletea dependency.

Ensure that the github.com/charmbracelet/bubbletea dependency is required for the project and there are no alternatives that might be more suitable.

---

71-71: Verify the necessity of github.com/charmbracelet/x/ansi dependency.

Ensure that the github.com/charmbracelet/x/ansi dependency is required for the project and there are no alternatives that might be more suitable.

---

72-72: Verify the necessity of github.com/charmbracelet/x/exp/strings dependency.

Ensure that the github.com/charmbracelet/x/exp/strings dependency is required for the project and there are no alternatives that might be more suitable.

---

73-73: Verify the necessity of github.com/charmbracelet/x/input dependency.

Ensure that the github.com/charmbracelet/x/input dependency is required for the project and there are no alternatives that might be more suitable.

---

74-74: Verify the necessity of github.com/charmbracelet/x/term dependency.

Ensure that the github.com/charmbracelet/x/term dependency is required for the project and there are no alternatives that might be more suitable.

---

75-75: Verify the necessity of github.com/charmbracelet/x/windows dependency.

Ensure that the github.com/charmbracelet/x/windows dependency is required for the project and there are no alternatives that might be more suitable.

---

76-76: Verify the necessity of github.com/containerd/console dependency.

Ensure that the github.com/containerd/console dependency is required for the project and there are no alternatives that might be more suitable.

---

80-80: Verify the necessity of github.com/erikgeiser/coninput dependency.

Ensure that the github.com/erikgeiser/coninput dependency is required for the project and there are no alternatives that might be more suitable.

---

81-81: Verify the necessity of github.com/felixge/httpsnoop dependency.

Ensure that the github.com/felixge/httpsnoop dependency is required for the project and there are no alternatives that might be more suitable.

---

83-83: Verify the necessity of github.com/go-logr/logr dependency.

Ensure that the github.com/go-logr/logr dependency is required for the project and there are no alternatives that might be more suitable.

---

84-84: Verify the necessity of github.com/go-logr/stdr dependency.

Ensure that the github.com/go-logr/stdr dependency is required for the project and there are no alternatives that might be more suitable.

---

97-97: Verify the necessity of github.com/gookit/color dependency.

Ensure that the github.com/gookit/color dependency is required for the project and there are no alternatives that might be more suitable.

---

105-105: Verify the necessity of github.com/jackc/puddle/v2 dependency.

Ensure that the github.com/jackc/puddle/v2 dependency is required for the project and there are no alternatives that might be more suitable.

---

113-114: Verify the necessity of github.com/lithammer/fuzzysearch and github.com/lucasb-eyer/go-colorful dependencies.

Ensure that the github.com/lithammer/fuzzysearch and github.com/lucasb-eyer/go-colorful dependencies are required for the project and there are no alternatives that might be more suitable.

---

117-117: Verify the necessity of github.com/mattn/go-localereader dependency.

Ensure that the github.com/mattn/go-localereader dependency is required for the project and there are no alternatives that might be more suitable.

---

118-118: Verify the necessity of github.com/mattn/go-runewidth dependency.

Ensure that the github.com/mattn/go-runewidth dependency is required for the project and there are no alternatives that might be more suitable.

---

121-121: Verify the necessity of github.com/muesli/ansi dependency.

Ensure that the github.com/muesli/ansi dependency is required for the project and there are no alternatives that might be more suitable.

---

122-122: Verify the necessity of github.com/muesli/cancelreader dependency.

Ensure that the github.com/muesli/cancelreader dependency is required for the project and there are no alternatives that might be more suitable.

---

123-123: Verify the necessity of github.com/muesli/termenv dependency.

Ensure that the github.com/muesli/termenv dependency is required for the project and there are no alternatives that might be more suitable.

---

127-127: Verify the necessity of github.com/rabbitmq/amqp091-go dependency.

Ensure that the github.com/rabbitmq/amqp091-go dependency is required for the project and there are no alternatives that might be more suitable.

---

129-129: Verify the necessity of github.com/rivo/uniseg dependency.

Ensure that the github.com/rivo/uniseg dependency is required for the project and there are no alternatives that might be more suitable.

---

146-150: Verify the necessity of go.opentelemetry.io dependencies.

Ensure that the go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc, go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, go.opentelemetry.io/otel, go.opentelemetry.io/otel/metric, and go.opentelemetry.io/otel/trace dependencies are required for the project and there are no alternatives that might be more suitable.

---

156-156: Verify the necessity of golang.org/x/term dependency.

Ensure that the golang.org/x/term dependency is required for the project and there are no alternatives that might be more suitable.