fix: issue37: sqluv binary release has the binary named as sqly

[nao1215]

Summary by CodeRabbit

• Chores

  • Updated the project’s identifier to the new name across configurations and settings.

• Documentation

  • Revised all descriptive text and references in documentation to ensure consistency with the updated project name.

[coderabbitai]

Walkthrough

This pull request renames the project identifier from sqly to sqluv across configuration and code comments. The change updates the project name in the .goreleaser.yml file and amends various comments in source files—including database configurations, domain logic descriptions, and repository interfaces—to reflect the new naming. No functional changes are made; the modifications strictly update descriptive text and metadata.

Changes

File(s)	Change Summary
.goreleaser.yml	Updated project_name from sqly to sqluv.
config/database.go, domain/errors.go, domain/model/history.go, domain/repository/history.go, infrastructure/persistence/history.go, interactor/history.go	Updated comments in various files to replace sqly references with sqluv (shell history, domain logic, records, and interface descriptions).

Possibly related issues

• [BUG] sqluv binary release has the binary named as sqly #37: Addresses the naming inconsistency by renaming the binary and related references from sqly to sqluv, aligning with the changes in this PR.

Poem

I'm a rabbit with a hop so bold,
Changing names in stories told.
From "sqly" to "sqluv", the code did sing,
A simple swap that makes our hearts spring.
Hopping in joy with every little change!
🐇✨

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[github-actions]

Code Metrics Report

	main (66346bb)	#38 (b33f75b)	+/-
Coverage	34.7%	34.7%	0.0%
Test Execution Time	40s	2s	-38s

Details

  |                     | main (66346bb) | #38 (b33f75b) | +/-  |
  |---------------------|----------------|---------------|------|
  | Coverage            |          34.7% |         34.7% | 0.0% |
  |   Files             |             27 |            27 |    0 |
  |   Lines             |            966 |           966 |    0 |
  |   Covered           |            336 |           336 |    0 |
+ | Test Execution Time |            40s |            2s | -38s |

Code coverage of files in pull request scope (12.5% → 12.5%)

Files	Coverage	+/-
config/database.go	10.9%	0.0%
domain/model/history.go	100.0%	0.0%
infrastructure/persistence/history.go	0.0%	0.0%
interactor/history.go	0.0%	0.0%

---

Reported by octocov

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/database.go (1)

272-283: Update HistoryDB Comment and Verify Config Parameter Spelling
The comment update from "sqly shell history" to "sqluv shell history" is correct and consistent with the overall renaming effort. However, please verify that the configuration field referenced as cfg.hisotryDBPath (line 278) is not a typographical error and should instead be spelled cfg.historyDBPath for clarity and consistency.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 66346bb and b28eaee.

📒 Files selected for processing (7)

• .goreleaser.yml (1 hunks)
• config/database.go (1 hunks)
• domain/errors.go (1 hunks)
• domain/model/history.go (1 hunks)
• domain/repository/history.go (1 hunks)
• infrastructure/persistence/history.go (1 hunks)
• interactor/history.go (1 hunks)

🔇 Additional comments (8)

domain/errors.go (1)

1-1: Update Package Comment for New Project Name
The package comment now correctly reflects "sqluv" instead of "sqly." This update is consistent with the new naming convention as outlined in the PR objectives.

interactor/history.go (1)

23-24: Update History Table Comment for Naming Consistency
The comment on the CreateTable method now refers to "sqluv history," aligning with the project’s new identifier. No functional changes were made, and the update improves consistency across the codebase.

infrastructure/persistence/history.go (1)

27-47: Update CreateTable Comment for Repository Consistency
The comment for the CreateTable method has been updated to "sqluv shell history," ensuring consistency with the new project name. The implementation remains unchanged and adheres to the intended functionality.

domain/repository/history.go (1)

12-16: Revise Repository Interface Comments to Reflect New Naming
The updated comments in the HistoryTableCreator interface now correctly mention "sqluv shell history," which aligns with the renaming across the project. There are no functional changes, and the update improves overall consistency.

.goreleaser.yml (1)

1-1: Project Name Update is Correct.
The updated project name on line 1 now correctly reflects the new identifier "sqluv", aligning with the intended naming update for binary releases.

domain/model/history.go (3)

7-7: Updated Comment for Histories.
The comment on the Histories type now uses "sqluv", ensuring consistency with the new project name.

---

10-10: Updated Comment for History Struct.
The comment for the History struct has been updated to reflect "sqluv" instead of "sqly", which aligns with the overall renaming effort.

---

14-14: Updated Comment for Request Field.
The comment for the Request field correctly states that it is a "sqluv history record that is user input from sqluv prompt", keeping the documentation consistent across the codebase.