All skills
gogf avatar

/goframe-v2

@911705d
by GoFramegogf/skills81 stars
3

GoFrame v2 development skill. Use only when the target Go project uses or is explicitly adopting GoFrame v2: the nearest go.mod requires github.com/gogf/gf/v2, existing Go files import github.com/gogf/gf/v2 or any github.com/gogf/gf/v2/... component package, or the user asks to scaffold, migrate, or build with GoFrame. Trigger for GoFrame-backed Go work such as APIs/controllers/services, middleware, routing/config, ORM/DAO/DO/entity/database operations, gf CLI/codegen, HTTP/gRPC services, and microservice conventions. Do not trigger for generic Go projects without GoFrame evidence, frontend-only work, shell scripts, or unrelated infrastructure tasks.

Use this Skill: https://skilld.dev/gh/gogf/skills/goframe-v2

This session only. Nothing lands on disk.

examplespracticesinjectionREADME.MD

≈1.3k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Dependency Injection Example

Introduction

This example demonstrates how to implement dependency injection in a GoFrame application.

Key demonstrations:

  1. Using monorepo pattern for code repository management
  2. Basic dependency injection setup
  3. Service layer implementation with DI
  4. Controller layer integration with gRPC
  5. Unit testing with mock dependencies

The implementation focuses on making core business logic easily testable:

  • Separation of concerns using dependency injection
  • Clear interfaces for service dependencies
  • Independent unit testing for each layer to ensure code quality

Requirements

Directory Structure

injection/
├── app/
│   ├── gateway/         # API Gateway service, calls user gRPC service for external interfaces
│   │   ├── api/         # API definitions
│   │   ├── internal/    # Internal implementations
│   │   │   ├── cmd/         # Command line tools
│   │   │   ├── controller/  # Controllers
│   │   │   ├── model/       # Data models
│   │   │   └── service/     # Business logic
│   │   └── manifest/   # Configuration files
│   └── user/           # User service
│       ├── api/        # API definitions
│       │   ├── entity/ # Entity definitions
│       │   └── user/   # User API proto
│       ├── internal/   # Internal implementations
│       │   ├── cmd/         # Command line tools
│       │   ├── controller/  # Controllers with DI
│       │   ├── dao/         # Data Access Objects
│       │   ├── model/       # Data models
│       │   └── service/     # Business logic with DI
│       └── manifest/   # Configuration files
├── hack/               # Development tools
└── utility/            # Common utilities
    ├── injection/      # DI utilities
    └── mongohelper/    # MongoDB helper tools

Features

  • Dependency injection usage
  • MongoDB and Redis integration
  • gRPC service implementation
  • Complete unit testing
  • Resource cleanup handling
  • Named dependency support

Installation

  1. Clone the repository:

    git clone https://github.com/gogf/examples.git
    cd examples/practices/injection
  2. Install dependencies:

    go mod tidy
  3. Start required services using Docker:

    # Start MongoDB
    docker run -d --name mongo -p 27017:27017 mongo:latest
    
    # Start Redis
    docker run -d --name redis -p 6379:6379 redis:latest

Usage

  1. Run the gRPC Server service:

    cd examples/practices/injection/app/user
    go run main.go server
  2. Run the HTTP Server service:

    cd examples/practices/injection/app/gateway
    go run main.go server
  3. (Optional) Run async worker, only demonstrates multi-command functionality, no actual logic:

    cd examples/practices/injection/app/gateway
    go run main.go worker
  4. (Optional) Run tests:

    go test ./...

Implementation Details

Dependency Injection Setup

  • Using github.com/samber/do package for dependency management
  • Support for named and unnamed dependency management
  • Helper functions for common operations

Service Layer

  • Clear separation of concerns
  • Interface-based design
  • Easy to test with mock implementations

Controller Layer

  • gRPC integration with DI support
  • Clear error handling
  • Proper resource management

Testability

  • Complete unit tests for data layer (dao), service layer (service), and interface layer (controller)
  • Mock dependencies, database configuration for unit tests managed through manifest/config
  • Service addresses or domains for microservice connections managed through configuration files for easy service mocking

Important Notes

  • Properly clean up resources in the Shutdown method when registering dependency injection
  • Use named dependencies when multiple instances of the same type are needed in dependency injection

Source: SKILL.md on GitHub

1 alert16d5 checks · Risk MEDIUM
  • Gen Agent Trust Hub16d

    The skill provides a comprehensive development guide and code examples for the GoFrame v2 framework. While highly informative for Go developers, it contains several examples with hardcoded placeholder secrets, tokens, and specific local file paths to sensitive configuration files (like Kubernetes credentials). These elements are provided for demonstration purposes but represent insecure practices if used in production without modification.

  • Socket16d

    5 alerts: gptSecurity, gptAnomaly

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    227/949 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 911705d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 months ago.

Steadyupdated 4 months ago
  • Go
  • Database
  • goframe
  • orm
  • http
  • grpc
  • microservices
  • crud
  • scaffolding
  • middleware

README badge

README badge for gogf/skills

Provides instruction and conventions for developing with GoFrame v2, a modular Go framework for building HTTP and gRPC services, microservices, and database operations using its ORM, CLI tooling, and project scaffolding. Use this skill when the target project has GoFrame v2 as a dependency or when the user requests scaffolding, migrations, or service development with GoFrame conventions.

Generated from the current SKILL.md.

When should I use this skill?
Use this skill only when your Go project uses GoFrame v2, indicated by github.com/gogf/gf/v2 in go.mod or imports. Do not use for generic Go projects, frontend work, or infrastructure tasks unrelated to GoFrame.
Should I manually set created_at and updated_at fields?
No. GoFrame automatically writes created_at on insert and updated_at on insert/update/save. Manually setting these fields is redundant and violates project conventions.
What should I use for database operations instead of g.Map?
Always use DO objects from internal/model/do/. DO struct fields are interface{}, unset fields remain nil and are automatically ignored by the ORM.
How does soft delete work in GoFrame?
Call Delete() on the DAO; GoFrame automatically converts it to UPDATE SET deleted_at = NOW(). Queries automatically filter out soft-deleted rows without requiring manual WhereNull conditions.
Where should I implement business logic?
Implement business logic directly in the service/ directory. Do not use the logic/ directory unless explicitly requested.

Generated from the current SKILL.md. These answers refresh after source changes.