Repository navigation
fix: stabilize environment editing and configurable PATH monitoring - #3
Merged
Merged
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
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.
Summary
Improve environment variable editing reliability and make PATH monitoring destinations configurable across user, machine, and global settings.
Inline editors now preserve row identity during refreshes, commit changes when clicking outside the active field, and handle unsaved changes consistently across navigation, dialogs, and window closing. Alias and version editors also respond correctly to window-level mouse events without interfering with their existing editing workflows.
External variable classification and PATH migration now support selectable destinations. Category menus prioritize the default External category, while PATH destination menus list eligible variables from the corresponding scope. Both allow creating new destinations directly. Default destinations are created when needed rather than prepopulated.
PATH organization, manual cleanup, CLI registration, and health checks now respect the configured destinations. Legacy
SOFTWARE_PATHnaming heuristics have been removed, so unrelated variables are no longer treated specially. Existing references remain intact, and stale monitoring conflict messages are cleared without hiding unresolved errors.The unified monitoring service also handles pending SCM state transitions when stopping or restarting, preventing failures during rapid configuration changes.
Testing
All CI checks passed.