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

Adding a "being processed" color/border/... to newly plated wells? Or vice versa.

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

还没有人认领这个 Issue。

评估

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

调研方向

未指定文件或测试。首先跟踪多次复制和粘贴的流程,以及粘贴的 wells 接收基于内容的格式化的节点;比较针对临时样式或初始样式提出的两种方案。完成的标准是:新粘贴的 wells 在处理期间有明显标记,并且在应用其正确的状态样式后移除该标记。

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

描述

front-end question

Using the fancy multiple-copy-and-pasting functionality :), if you paste in a bunch of things at once then there's a sometimes-brief period where some of the wells pasted in have a white background, even if they really shouldn't. See the attached screenshot, where I pasted in the same ID to a bunch of cells—only some of the cells' formatting has changed to reflect the fact that this text is 1) duplicated on this plate and 2) previously plated.

Since "plain white background" is the implied status of "this is a good ID," the current behavior is somewhat misleading. I propose one of the following options:

  • Option 1: Modified wells are immediately (before anything else is done) assigned a unique styling, say a dashed-gray border, indicating that they are being processed and will update soon. This shouldn't require a backend update, since there isn't any need to store this information long-term (similarly to how #585 handles indeterminate wells)—this would just involve temporarily applying this styling, then removing it later.
  • Option 2: All wells on a plate start off with a similar styling (in this case indicating "not processed yet"), and this styling is removed when a well is assigned a style relating to its contents.

...As I was writing this out I realized that implementing this would be a pain, but I still think it might be worth doing later on down the line if the current behavior is confusing.

主要语言
Python
星标
2
派生
15
PR 合并指标
30 天内没有已合并 PR

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

biocore/LabControl 的其他 Issue

查看 biocore/LabControl 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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