feat: [#540] Move the Postgres driver to a single package

[hwbrzzl]

📑 Description

Closes goravel/goravel#540

Summary by CodeRabbit

Release Notes for Goravel Postgres Driver v1.0.0

• New Features

  • Added comprehensive PostgreSQL driver support for Goravel framework
  • Implemented schema management, GORM integration, and database configuration
  • Enhanced database schema processing and grammar generation

• Documentation

  • Updated README with installation and configuration instructions
  • Added version compatibility table for Goravel framework

• Infrastructure

  • Introduced GitHub Actions workflows for testing, linting, and code coverage
  • Updated repository configuration and issue templates

• Chores

  • Updated project dependencies
  • Refined code structure and utility functions

✅ Checks

• Added test cases for my code

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request introduces a comprehensive implementation of a PostgreSQL driver for the Goravel framework. The changes involve creating a dedicated package for PostgreSQL database operations, including configuration management, schema handling, GORM integration, and utility functions. The implementation provides a modular approach to database interactions, with support for various database schema operations, connection management, and testing infrastructure.

Changes

File	Change Summary
.github/*	Added configuration files for code owners, issue templates, and GitHub Actions workflows
README.md	Added version compatibility table and installation/configuration instructions for Postgres driver
config.go, contracts/config.go	Updated configuration handling, removed MySQL-specific fields
docker.go, docker_test.go	Modified Docker-related functionality for Postgres
facades/postgres.go	Updated Postgres facade with new driver interface
go.mod	Updated dependencies and framework version
gorm.go, grammar.go, processor.go, schema.go, wrap.go	Implemented core Postgres driver functionality with comprehensive methods for database operations
service_provider.go	Enhanced error handling for driver registration
utils.go	Added utility functions for type handling and schema parsing

Assessment against linked issues

Objective	Addressed	Explanation
Move DB drivers to separate packages	✅	Implemented a dedicated goravel/postgres package with comprehensive functionality
Postgres as default DB driver	❓	Requires further verification in framework configuration

Sequence Diagram

sequenceDiagram
    participant App as Application
    participant Provider as ServiceProvider
    participant Postgres as Postgres Driver
    participant Config as Configuration
    participant ORM as GORM
    participant Schema as Schema Handler

    App->>Provider: Register Postgres Driver
    Provider->>Config: Retrieve Configuration
    Provider->>Postgres: Initialize Driver
    Postgres->>ORM: Configure Connection
    Postgres->>Schema: Set Up Schema Handling
    App->>Postgres: Perform Database Operations

Loading

The sequence diagram illustrates the initialization and usage of the Postgres driver within the Goravel framework, showing how the driver is registered, configured, and prepared for database interactions.

---

📜 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 6fdc34a and 852b75c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (27)

• .github/CODEOWNERS (1 hunks)
• .github/ISSUE_TEMPLATE/config.yml (1 hunks)
• .github/workflows/codecov.yml (1 hunks)
• .github/workflows/lint.yml (1 hunks)
• .github/workflows/pr-check-title.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)
• README.md (1 hunks)
• config.go (3 hunks)
• config_test.go (7 hunks)
• contracts/config.go (1 hunks)
• docker.go (3 hunks)
• docker_test.go (1 hunks)
• facades/postgres.go (1 hunks)
• go.mod (2 hunks)
• gorm.go (1 hunks)
• grammar.go (1 hunks)
• grammar_test.go (1 hunks)
• postgres.go (2 hunks)
• postgres_test.go (1 hunks)
• processor.go (1 hunks)
• processor_test.go (1 hunks)
• schema.go (1 hunks)
• service_provider.go (2 hunks)
• utils.go (3 hunks)
• utils_test.go (1 hunks)
• wrap.go (1 hunks)
• wrap_test.go (1 hunks)

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.