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 temperature step form #17447

Merged
merged 2 commits into from
Feb 6, 2025

Conversation

ncdiehl11
Copy link
Collaborator

Overview

This PR fixes a bug in the temperature step form where a form error is incorrecly returned if a user has not entered a temperature, even if the setTemperature ield is set to false. The error arose from incorrectly parsing the string literals for 'true' / 'false'. Also, this PR fixes the step summary text for deactivating a temperature module

Closes RQA-3947, RQA-3948

Test Plan and Hands on Testing

  • create or import a protocol with a temperature module
  • create a new temperature step
  • toggle on 'module state', and enter a value for temperature
  • toggle off again, and verify that save works properly
  • select or hover that new step, and verify that step summary reads: "[temperature module model] deactivated"

Changelog

  • fix temperature required form error logic
  • fix step summary ternary condition

Review requests

see test plan

Risk assessment

low

This PR fixes a bug in the temperature step form where a form error is incorrecly returned if a user has not entered a temperature, even if the setTemperature ield is set to false. The error arose from incorrectly parsing the string literals for 'true' / 'false'. Also, this PR fixes the step summary text for deactivating a temperature module

Closes RQA-3947, RQA-3948
@ncdiehl11 ncdiehl11 requested review from koji and jerader February 6, 2025 16:56
@ncdiehl11 ncdiehl11 self-assigned this Feb 6, 2025
@ncdiehl11 ncdiehl11 marked this pull request as ready for review February 6, 2025 16:57
@ncdiehl11 ncdiehl11 requested a review from a team as a code owner February 6, 2025 16:57
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.

thank you for fixing!

@ncdiehl11
Copy link
Collaborator Author

Note, we should probably refactor the implementation of string values where they really should be booleans.

@koji
Copy link
Contributor

koji commented Feb 6, 2025

Note, we should probably refactor the implementation of string values where they really should be booleans.

you mean update FormData type?

@ncdiehl11 ncdiehl11 merged commit 09e127d into chore_release-pd-8.4.0 Feb 6, 2025
14 checks passed
@ncdiehl11 ncdiehl11 deleted the fix_pd-temp-form branch February 6, 2025 18:24
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