fix: resolve personal environments correctly while editing via quick peek #4384
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
|
@AndrewBastin please, review it. |
nivedin
force-pushed
the
quick-edit-bug
branch
from
ba0d5aa
to
3ef7940
Compare
nivedin
approved these changes
Oct 8, 2024
jamesgeorge007
changed the title
jamesgeorge007
approved these changes
Oct 10, 2024
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.
Previously, attempting to edit the active environment under personal workspace entry via
Environment Quick Peekwill result in the modal getting displayed with variables from another environment entry. This PR includes a fix for the same.Closes #4380
What's changed
Fixed a function to define current env by name