Conversation
deeab9e to
7018b6f
Compare
|
Update: I have removed the alert that indicates this Outdated: Added a change here for when the source items for list creation are not from the current history (the created collection still goes to the current history even if the source one is different): pairing_wizard_tweaks.mp4 |
ahmedhamidawan
left a comment
There was a problem hiding this comment.
Other than minor tweaks I added (as mentioned in the comment above), the help text additions/improvements make sense to me!
I don't think we should show this, that's a lot of text taking up a lot of space, why would you think that's not the behavior ? My usual comment, no one was concerned about this before it was mentioned ? :) |
I just felt like it gives the user content that the output collection will go into the current history, and not the history the datasets are from. I don't mind removing the alert. Would it be worth putting a warning |
|
I would not do that, we should keep warning for actual warnings. |
- Add help text under filter boxes explaining forward/reverse pair naming - Update paired datasets description with Illumina/ElementBio examples - Display unmatched datasets as bulleted list instead of inline comma-separated Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
For some reason, we had these direction labels set as `display: none`.
7018b6f to
e7bc860
Compare
I have dropped the commit that adds the alert |
Summary
How to test the changes?
(Select all options that apply)
/collection/new_list?advanced=true(by selecting a few datasets from your history, and choosing the "Advanced Build List" selection operation)🤖 Generated with Claude Code