Adding a "being processed" color/border/... to newly plated wells? Or vice versa.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No file or test is named. Start by tracing the multiple-copy-and-paste flow and the point where pasted wells receive content-based formatting; compare the two proposed approaches for temporary or initial styling. Done means newly pasted wells are visibly marked while processing and the marker is removed once their correct status styling is applied.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 2
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from biocore/LabControl
-
bug front-end question
Difficulty 4/5 3-5 days Newbie friendliness 30/100
biocore/LabControl#594 ·
-
front-end
biocore/LabControl#592 · 1 assignee ·
-
code refactor front-end
Difficulty 5/5 Over a week Newbie friendliness 25/100
biocore/LabControl#591 ·
-
priority:low
Difficulty 3/5 1-2 days Newbie friendliness 20/100
biocore/LabControl#590 ·
-
priority:low scope:small
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
biocore/LabControl#589 · 2 comments ·
All issues in biocore/LabControl
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·