chore: [#539] Remove the SQL migrator module

[hwbrzzl]

📑 Description

Closes goravel/goravel#539

Summary by CodeRabbit

Release Notes

• Refactoring

  • Renamed migration-related structs and methods from DefaultMigrator to Migrator
  • Simplified migrator initialization process
  • Removed SQL-specific migration implementations, including SQL creator and migrator files

• Dependency Changes

  • Updated and cleaned up project dependencies
  • Removed several external migration and database-related libraries

• Code Cleanup

  • Removed SQLite driver implementation
  • Streamlined migration service provider configuration

• Error Handling

  • Maintained existing migration-related error messages

These changes represent a significant refactoring of the database migration system, focusing on simplifying the implementation and reducing complexity.

✅ Checks

• Added test cases for my code

[coderabbitai]

Walkthrough

This pull request involves the removal of the SQL migrator module and several associated files within the database migration system. Key changes include the deletion of the SQLite driver, SQL-related migration files, and the refactoring of core migration-related structs and methods, such as renaming DefaultCreator to Creator and DefaultMigrator to Migrator. The changes aim to simplify the migration implementation and standardize the approach across different database drivers.

Changes

File	Change Summary
database/console/driver/sqlite.go	Entire file removed
database/migration/creator.go	Renamed DefaultCreator to Creator and updated method signatures
database/migration/creator_test.go	Updated test suite to use new Creator type
database/migration/migrator.go	Renamed DefaultMigrator to Migrator and updated method signatures
database/migration/migrator_test.go	Updated test cases to use new Migrator type
database/migration/sql_creator.go	Entire file removed
database/migration/sql_creator_test.go	Entire file removed
database/migration/sql_migrator.go	Entire file removed
database/migration/sql_migrator_test.go	Entire file removed
database/service_provider.go	Simplified migrator initialization
go.mod	Removed several dependencies related to SQL migration and Azure

Assessment against linked issues

Objective	Addressed	Explanation
Remove SQL migrator module	✅	All SQL migrator-related files have been deleted

Possibly related PRs

• feat: [#280] Manage migrations table #664: The changes in this PR involve the introduction of new methods for managing migrations, which may relate to the overall migration functionality impacted by the removal of the SQLite driver in the main PR.
• feat: [#280] Optimize migration command #680: This PR focuses on optimizing the migration command, which is directly related to the migration functionalities that were affected by the removal of the SQLite driver in the main PR.
• feat: [#280] Optimize migrate:status command #696: The addition of new methods for migration management in this PR aligns with the changes made in the main PR regarding the migration system.
• feat: [#280] Implement Sqlserver driver #726: The implementation of the SQL Server driver in this PR is relevant as it expands the migration capabilities that were impacted by the removal of the SQLite driver in the main PR.
• feat: [#280] Add some methods for Schema #747: This PR adds methods for schema management, which is related to the migration functionalities that were altered in the main PR.
• feat: improve artisan migrate:status command #780: Enhancements to the migrate:status command in this PR are directly related to the migration functionalities that were affected by the removal of the SQLite driver in the main PR.

Suggested reviewers

• kkumar-gcc

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 586e4b6 and c81ce91.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (12)

• database/console/driver/sqlite.go (0 hunks)
• database/migration/creator.go (3 hunks)
• database/migration/creator_test.go (1 hunks)
• database/migration/migrator.go (14 hunks)
• database/migration/migrator_test.go (8 hunks)
• database/migration/sql_creator.go (0 hunks)
• database/migration/sql_creator_test.go (0 hunks)
• database/migration/sql_migrator.go (0 hunks)
• database/migration/sql_migrator_test.go (0 hunks)
• database/service_provider.go (1 hunks)
• errors/list.go (1 hunks)
• go.mod (4 hunks)

💤 Files with no reviewable changes (5)

• database/migration/sql_creator.go
• database/console/driver/sqlite.go
• database/migration/sql_creator_test.go
• database/migration/sql_migrator_test.go
• database/migration/sql_migrator.go

🚧 Files skipped from review as they are similar to previous changes (5)

• errors/list.go
• database/migration/creator_test.go
• database/migration/creator.go
• go.mod
• database/migration/migrator.go

🧰 Additional context used

🪛 GitHub Check: codecov/patch

database/service_provider.go

[warning] 84-84: database/service_provider.go#L84
Added line #L84 was not covered by tests

⏰ Context from checks skipped due to timeout of 300000ms (2)

• GitHub Check: test / windows (1.23)
• GitHub Check: test / windows (1.22)

🔇 Additional comments (4)

database/service_provider.go (2)

Line range hint 84-98: LGTM! The migrator initialization and command registration look good.

The changes align with the PR objective of removing the SQL migrator module. The code is now more straightforward with direct initialization of the migrator.

🧰 Tools

🪛 GitHub Check: codecov/patch

[warning] 84-84: database/service_provider.go#L84
Added line #L84 was not covered by tests

---

84-84: Add test coverage for migrator initialization.

The line initializing the migrator with migration.NewMigrator is not covered by tests.

Run this script to verify test coverage:

🧰 Tools

🪛 GitHub Check: codecov/patch

[warning] 84-84: database/service_provider.go#L84
Added line #L84 was not covered by tests

database/migration/migrator_test.go (2)

87-87: LGTM! Constructor calls correctly updated.

The migrator constructor calls have been consistently updated from NewDefaultMigrator to NewMigrator across all test cases.

Also applies to: 107-107, 126-126, 141-141, 181-181, 205-205

---

218-218: LGTM! Type and initialization changes are consistent.

The changes reflect the refactoring:

• Updated type from *DefaultMigrator to *Migrator
• Updated creator initialization from NewDefaultCreator() to NewCreator()

Also applies to: 230-234

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[codecov]

Codecov Report

Attention: Patch coverage is 96.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 69.57%. Comparing base (9f64a3c) to head (c81ce91).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
database/service_provider.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #809      +/-   ##
==========================================
- Coverage   69.78%   69.57%   -0.22%     
==========================================
  Files         218      215       -3     
  Lines       18876    18499     -377     
==========================================
- Hits        13172    12870     -302     
+ Misses       4988     4962      -26     
+ Partials      716      667      -49     

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