Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Should external IDs be contrained to be unique?

未关闭
#952 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
database

调研方向

Start by reading the participant import flows for the invite modal and CSV upload, then locate where the external ID is stored and validated. The issue raises competing concerns but does not settle whether IDs should be unique; first clarify the intended behavior with maintainers. Done would mean implementing the agreed behavior consistently across both import paths.

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

描述

question

Currently there is no unique contraint on the external ID field when importing participants via invite modal or CSV upload.

Conceptually, that is strange to me as I'd expect an external ID to be an ID for a participant and therefore should be unique. Adding a unique constraint might help prevent accidental data input errors by study admins (or help catch bad data).

Conversely, we don't yet know how people are going to use the external id field, and so it might be okay to not have a unique constraint on that field.

I feel like the conservative position is safest until we get asked for a use-case for the alternative, but I'm happy to hear counter arguments!

主要语言
TypeScript
星标
4
派生
0
平均合并
14 小时 50 分钟
30 天内合并 PR
5

环境准备

从这里开始

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

Garvan-Data-Science-Platform/ctrl 的其他 Issue

查看 Garvan-Data-Science-Platform/ctrl 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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