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.

referencesWEB服务开发路由管理路由管理-中间件拦截器中间件拦截器-常见问题.md

如何通过中间件修改请求参数

在了解如何修改请求参数之前,请先了解一下请求参数输入的一些细节知识: 请求输入🔥

自定义参数覆盖

修改请求参数最简单的方式,是通过 自定义参数 来覆盖客户端提交的参数。因为自定义参数在参数解析的优先级最高,因此在 全量获取请求参数(不是通过特定的提交方式获取参数)时,会使用自定义参数来覆盖掉其他提交方式的参数。这种修改方式比较常见,特别是使用规范路由时,接收参数时一个 struct 对象,底层是通过全量获取参数后再转换为 struct 对象。

但是如果用户是用过 r.GetQuery, r.GetForm 来获取参数时,自定义参数覆盖将会失效。而 r.Get 或者 r.GetRequest 方式获取参数,也可以实现参数覆盖的效果。

修改特定请求方式的参数

也可以在中间件中通过修改 r.URL.RawQuery 或者 r.Body 来修改原始参数,但是在修改完毕后,需要调用 r.ReloadParam() 来标识下一次获取请求参数时将重新解析参数。

通过中间件修改请求Body的注意事项

当通过中间件修改 r.Body 时常遇到的一个问题,是 r.Body 只允许读取一次,后续的读取都将读取不到数据,这是标准库 http.Request 的设计。在 GoFrame 框架的 ghttp.Request 对象中,允许通过框架 ghttp.Request 的 GetBody、 GetBodyString 方法连续读取 Body 内容。

但是,如果是在中间件中自行通过标准库 http.Request 对象直接读取 r.Body,那么建议通过重新赋值 r.Body 或者通过 io.NopCloser 重新包裹赋值给 r.Body 便于后续中间件或者流程进一步读取 Body 内容。

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.