Concept detail with `includeInverseMappings=true` returns every inverse mapping, unpaginated

未关闭
#2,937 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
api

调研方向

Compare the concept detail endpoint with the mappings list URL described in the issue to understand how inverse mappings are included and paginated. First clarify the proposed response behavior with the TBv2 and TBv3 owners; then check the endpoint documentation and relevant API tests. Done means the agreed cap, total and paging URL (or caller guidance) are covered, with tests for the large result set.

由索引模型根据 Issue 内容生成。

描述

component/api decision/human-review program/platform-health signal/needs-human signal/small-scope stage/triaged type/bug

GET /orgs/CIEL/sources/CIEL/concepts/1065/?includeMappings=true&includeInverseMappings=true returns 869 mappings (1.39 MB) and takes 1.2–2.5 s. Several LOINC concepts, e.g. 72230-6 and LA6577-6, have 6,000–7,200 inverse mappings in their own source, so their responses would run to many MB.

The repository's mappings list, …/mappings/?toConcept=…&toConceptSource=…&toConceptOwner=…, already pages and counts the same set, in about 0.3 s.

  • Concept detail caps the inverse mappings it includes inline (e.g. at 100), and reports the total and the list URL that pages through the rest. Or the docs point callers to the list.
  • The change to default behaviour is agreed with the TBv2 and TBv3 owners.
主要语言
没有语言数据
星标
4
派生
2
平均合并
2 小时 12 分钟
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenConceptLab/ocl_issues 的其他 Issue

查看 OpenConceptLab/ocl_issues 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。