Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(protocol-designer): fix save behavior for bad liquid form #17171

Open
wants to merge 1 commit into
base: edge
Choose a base branch
from

Conversation

ncdiehl11
Copy link
Collaborator

@ncdiehl11 ncdiehl11 commented Dec 23, 2024

Overview

In liquids toolbox, we should never disable "save" when adding a liquid to wells. Rather, errors should show when save is clicked, surfacing to the user fields that need to be resolved. Here, I modify our logic for Controller rules in our form used to added liquids, and implement a volume validation function.

Closes RQA-3497

Test Plan and Hands on Testing

Screen.Recording.2024-12-23.at.2.41.59.PM.mov
  • open "add/edit liquid" from a labware on starting deck
  • select wells to open add liquid form
  • verify behavior for various error states (empty and invalid volumes)

Changelog

  • update form logic
  • add translations

Review requests

see test plan

Risk assessment

low

In liquids toolbox, we should never disable "save" when adding a liquid to wells. Rather, errors should show when save is clicked, surfacing to the user fields that need to be resolved. Here, I modify our logic for Controller rules in our form used to added liquids, and implement a volume validation function.

Closes RQA-3497
@ncdiehl11 ncdiehl11 self-assigned this Dec 23, 2024
@ncdiehl11 ncdiehl11 requested review from koji and jerader December 23, 2024 19:50
@ncdiehl11 ncdiehl11 marked this pull request as ready for review December 23, 2024 20:32
@ncdiehl11 ncdiehl11 requested a review from a team as a code owner December 23, 2024 20:32
Copy link
Contributor

@koji koji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the changes look good to me and it worked as expected.
seems that no.2 is fixed already.
will you plan to fix no.3 in another pr?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants