Improve beneathPath to work with multiple nested arrays
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- java
- 领域
- api, documentation
调研方向
Start by tracing the beneathPath() entry point with the nested roles and more payload shown in the issue, comparing beneathPath("roles[].more") with the single-array case. The change is done when the nested array can be documented with fieldWithPath("id") and generated paths no longer begin with [].
由索引模型根据 Issue 内容生成。
描述
In beneathPath(), paths with an array work now, thanks to #473 and 9e1ba8a. But I'm still having a problem with arrays when there are two levels of arrays in the payload.
Consider the payload:
{
"roles": [
{
"key": "1",
"name": "one",
"more": [
{
"id": 1
}
]
},
{
"key": "1",
"name": "one",
"more": []
}
]
}
And I document it like so:
document(snippetName,
responseFields(
// beneathPath understands that roles is an array and does the right thing
beneathPath("roles").withSubsectionId("roles"),
fieldWithPath("key").description("key"),
fieldWithPath("name").description("name"),
subsectionWithPath("more").description("array")));
This will give me the fields of roles with a description of the more property. To then document the object within the more array, I do a separate snippet:
document(snippetName,
responseFields(
// now beneathPath doesn't deal with 'roles' here like it does above
beneathPath("roles[].more").withSubsectionId("more"),
fieldWithPath("[].id").description("id")));
The issue here is that at this point, the second array, the problem is the same as #473, you get a snippet with [] in front of the field path, which is functional, but not great from a documentation standpoint, which is the whole point.
To make this work like the single array, I'd expect maybe beneathPath("roles.more") to work with fieldWithPath("id"), giving me a table with Paths like id in this case.
- 主要语言
- Java
- 星标
- 1.2k
- 派生
- 733
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
spring-projects/spring-restdocs 的其他 Issue
-
status: waiting-for-triage
难度 4/5 3-5 天 新手友好度 35/100
spring-projects/spring-restdocs#1075 ·
-
Support extracting Bean Validation constraints from method parameters可能重新可做 关联的 PR 已关闭且未合并。 未关闭status: waiting-for-triage
难度 5/5 一周以上 新手友好度 45/100
spring-projects/spring-restdocs#1026 · 2 条评论 ·
-
status: blocked status: waiting-for-triage
难度 4/5 3-5 天 新手友好度 35/100
spring-projects/spring-restdocs#953 · 7 条评论 ·
-
Add support for modifying a URI's path during pre-processing可能重新可做 关联的 PR 已关闭且未合并。 未关闭type: enhancement
难度 3/5 1-2 天 新手友好度 45/100
-
status: feedback-provided status: waiting-for-triage
难度 3/5 1-2 天 新手友好度 45/100
spring-projects/spring-restdocs#937 · 4 条评论 ·
查看 spring-projects/spring-restdocs 的全部 Issue
相似的 Issue
-
BindingServiceProperties.bindings regressed to a non-thread-safe TreeMap in GH-3158: concurrent first use of binding names corrupts it可能已有人在做 @AkashB23 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
spring-cloud/spring-cloud-stream#3321 ·
维护者通常 1 天内回复
-
[Bug] 资源包列表 与 模组/数据包/世界 列表排列顺序不一致可能已有人在做 @fishdry1000 于 4 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
ai-driven-fuzzing bug claude Minor
难度 2/5 1-3 小时 新手友好度 72/100
linagora/twake-calendar-side-service#1333 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
AtlasOfLivingAustralia/species-lists#882 ·
维护者通常 1 天内回复
-
Type/Bug
难度 2/5 1-3 小时 新手友好度 62/100
ballerina-platform/ballerina-library#9458 ·
维护者通常 1 天内回复