-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need tag in:header
works in router definition
#2060
Labels
planned
This issue/proposal is planned into our next steps.
Comments
能否提供最小代码 |
|
跟 #2036 的问题一样 |
mingzaily
added
bug
It is confirmed a bug, but don't worry, we'll handle it.
feature
and removed
bug
It is confirmed a bug, but don't worry, we'll handle it.
labels
Aug 12, 2022
和社区小伙伴讨论了下,文档中的in只是给openapi的展示,解析参数并未支持,后续会添加功能 |
假如现在需要从header中取数据,可以现在先这样 r := g.RequestFromCtx(ctx)
r.GetHeader("AppKey") 或使用中间件处理 |
目前还没进到 Index 方法就 error 了 |
可以使用中间件或先取消header参数的必传验证 |
gqcn
added
planned
This issue/proposal is planned into our next steps.
and removed
feature
inactive
labels
Jan 18, 2023
计划分几步操作
|
gqcn
changed the title
规范路由注册时,参数设置为 in:"header",生成api.json正常(有header参数),但是调用接口时框架无法解析这个参数
need tag Mar 7, 2023
in:header
works in router definition
@sanrentai 目前已经支持了 |
@sanrentai is currently supported |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1. What version of
Go
and system type/arch are you using?go version go1.17.1 windows/amd64
2. What version of
GoFrame
are you using?v2.1.1
3. Can this issue be re-produced with the latest release?
yes
4. What did you do?
5. What did you expect to see?
正常解析参数
6. What did you see instead?
业务系统唯一码不能为空
The text was updated successfully, but these errors were encountered: