docs: LLD and liquid classes #19806
Merged
docs: LLD and liquid classes #19806
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
emilyburghardt
commented
Oct 15, 2025
emilyburghardt
commented
Oct 15, 2025
emilyburghardt
commented
Oct 15, 2025
emilyburghardt
commented
Oct 15, 2025
emilyburghardt
commented
Oct 21, 2025
jwwojak
reviewed
Oct 21, 2025
Contributor
jwwojak
left a comment
jwwojak
left a comment
There was a problem hiding this comment.
Ye olde HTML suggestion included, free!
ecormany
reviewed
Oct 22, 2025
Contributor
ecormany
left a comment
ecormany
left a comment
There was a problem hiding this comment.
LLD additions are good. The Introduction refactor needs some additional work, which you can either do here or move to a separate PR, since it's not focused on the LLD feature.
jwwojak
approved these changes
Oct 29, 2025
Contributor
jwwojak
left a comment
jwwojak
left a comment
There was a problem hiding this comment.
Just one comment, LGTM.
Still think you should use suspended hyphens though. 😜
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## edge #19806 +/- ##
==========================================
+ Coverage 24.23% 25.48% +1.25%
==========================================
Files 3540 3540
Lines 298345 298348 +3
Branches 39863 39863
==========================================
+ Hits 72298 76048 +3750
+ Misses 226029 222276 -3753
- Partials 18 24 +6
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
emilyburghardt
force-pushed
the
docs-Flex-exclusives-liquids
branch
from
c744bc6 to
f17a34f
Compare
emilyburghardt
force-pushed
the
docs-Flex-exclusives-liquids
branch
from
f6505c3 to
e4bf7d9
Compare
ecormany
approved these changes
Nov 3, 2025
Contributor
ecormany
left a comment
ecormany
left a comment
There was a problem hiding this comment.
Good additions. We will surely have more to say about LLD in the future, but let's get this committed for now.
ecormany
changed the title
koji
pushed a commit
that referenced
this pull request
Nov 3, 2025
<!-- Thanks for taking the time to open a Pull Request (PR)! Please make sure you've read the "Opening Pull Requests" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests GitHub provides robust markdown to format your PR. Links, diagrams, pictures, and videos along with text formatting make it possible to create a rich and informative PR. For more information on GitHub markdown, see: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax To ensure your code is reviewed quickly and thoroughly, please fill out the sections below to the best of your ability! --> # Overview reworking the "what's new on Flex" section > "Flex-exclusive features" for a few reasons: - the OT-2 and Flex comparison is no longer what's most important in the introduction. here, I've walked back the comparison text (but still include a small section to do so). - this section can be useful to us to describe what's different/exclusive to Flex without comparison. This can also be a soft landing place for new features that aren't ready for an entire section, but will be one day (like LLD. After 8.8, this could very well get its own section). -also sprinkling throughout: LLD, liquid classes, a mention of liquid classes in QT. Trying to bridge the gap before some of these features get more new shiny things added to them and can have their own section (LLD mostly). <!-- Describe your PR at a high level. State acceptance criteria and how this PR fits into other work. Link issues, PRs, and other relevant resources. --> ## Test Plan and Hands on Testing <!-- Describe your testing of the PR. Emphasize testing not reflected in the code. Attach protocols, logs, screenshots and any other assets that support your testing. --> ## Changelog <!-- List changes introduced by this PR considering future developers and the end user. Give careful thought and clear documentation to breaking changes. --> ## Review requests <!-- - What do you need from reviewers to feel confident this PR is ready to merge? - Ask questions. --> ## Risk assessment <!-- - Indicate the level of attention this PR needs. - Provide context to guide reviewers. - Discuss trade-offs, coupling, and side effects. - Look for the possibility, even if you think it's small, that your change may affect some other part of the system. - For instance, changing return tip behavior may also change the behavior of labware calibration. - How do your unit tests and on hands on testing mitigate this PR's risks and the risk of future regressions? - Especially in high risk PRs, explain how you know your testing is enough. -->
CaseyBatten
pushed a commit
that referenced
this pull request
Nov 4, 2025
<!-- Thanks for taking the time to open a Pull Request (PR)! Please make sure you've read the "Opening Pull Requests" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-pull-requests GitHub provides robust markdown to format your PR. Links, diagrams, pictures, and videos along with text formatting make it possible to create a rich and informative PR. For more information on GitHub markdown, see: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax To ensure your code is reviewed quickly and thoroughly, please fill out the sections below to the best of your ability! --> # Overview reworking the "what's new on Flex" section > "Flex-exclusive features" for a few reasons: - the OT-2 and Flex comparison is no longer what's most important in the introduction. here, I've walked back the comparison text (but still include a small section to do so). - this section can be useful to us to describe what's different/exclusive to Flex without comparison. This can also be a soft landing place for new features that aren't ready for an entire section, but will be one day (like LLD. After 8.8, this could very well get its own section). -also sprinkling throughout: LLD, liquid classes, a mention of liquid classes in QT. Trying to bridge the gap before some of these features get more new shiny things added to them and can have their own section (LLD mostly). <!-- Describe your PR at a high level. State acceptance criteria and how this PR fits into other work. Link issues, PRs, and other relevant resources. --> ## Test Plan and Hands on Testing <!-- Describe your testing of the PR. Emphasize testing not reflected in the code. Attach protocols, logs, screenshots and any other assets that support your testing. --> ## Changelog <!-- List changes introduced by this PR considering future developers and the end user. Give careful thought and clear documentation to breaking changes. --> ## Review requests <!-- - What do you need from reviewers to feel confident this PR is ready to merge? - Ask questions. --> ## Risk assessment <!-- - Indicate the level of attention this PR needs. - Provide context to guide reviewers. - Discuss trade-offs, coupling, and side effects. - Look for the possibility, even if you think it's small, that your change may affect some other part of the system. - For instance, changing return tip behavior may also change the behavior of labware calibration. - How do your unit tests and on hands on testing mitigate this PR's risks and the risk of future regressions? - Especially in high risk PRs, explain how you know your testing is enough. -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
reworking the "what's new on Flex" section > "Flex-exclusive features" for a few reasons:
-also sprinkling throughout: LLD, liquid classes, a mention of liquid classes in QT. Trying to bridge the gap before some of these features get more new shiny things added to them and can have their own section (LLD mostly).
Test Plan and Hands on Testing
Changelog
Review requests
Risk assessment