fix(common): ensure the add-environment modal value field is empty when opened via the inspector #3664
Conversation
This file contains 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
…d via the inspector
liyasthomas
approved these changes
Dec 18, 2023
jamesgeorge007
commented
Dec 18, 2023
nivedin
approved these changes
Dec 18, 2023
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.
Description
When opened via the inspector, the add environment modal showed the value associated with the previous attempt to set an environment via the context menu. This PR aims to fix this behavior by removing the truthy check before assigning environment values at the parent environments component, thereby permitting empty strings.
Screen.Recording.2023-12-18.at.2.07.57.PM.mov
Closes HFE-347.
Checks