Rebuild every expansion's explicit and evaluated repo version lists

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
databases

调研方向

Start with the expansion reference and member handling in the oclapi2 repository, then inspect the existing version locking behavior and FHIR parity tests. The issue requires a rebuild command, a dry run, production review, and a release note, but does not name the relevant files or tests. Done means the lists follow the stated reference rules, members remain unchanged, and the parity subset passes.

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

描述

component/api decision/blocked signal/has-dependencies signal/high-risk signal/needs-access signal/needs-human signal/well-specified stage/triaged type/feature

Repo: oclapi2 · Depends on: OpenConceptLab/ocl_online#586's toggle on in production

Part of OpenConceptLab/ocl_issues#2942; the unchecked criterion of OpenConceptLab/ocl_issues#2236. Expansions built before version locking list every repo version as explicit, because the backfill never ran, and some list a version in both lists. Members stay as they are, but later adds and FHIR read these lists, so what they say starts to matter.

ACs

  • A command rebuilds each expansion's lists from its references and members: versions that repo-versioned and resource-versioned references name or use are explicit; versions that unversioned references resolved to are evaluated; no version is in both.
  • No member changes, proved by a test and by the dry run.
  • A dry run reports per expansion what would change, including expansions that would gain a lock, and states the rule used when members come from several repo versions.
  • A FHIR parity subset passes before the production run.
  • Production: dry run reviewed, Jon's OK, before and after copies filed.
  • A release note tells self-hosted installs to run it after upgrading.
主要语言
没有语言数据
星标
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

更多 Databases Issue

把新 issue 发到你的邮箱

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