Clarify empty PSCommander config startup#3
Merged
Conversation
Handle empty config.ps1 files by writing the starter toolbar configuration, matching the missing-file startup behavior. Update README guidance to explain that configuration commands belong in config.ps1 and are not automatically persisted from an interactive session. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Starting PSCommander with a manually created empty
config.ps1looked like nothing happened, because the starter configuration was only written when the file was missing. This makes the empty-file path behave like first-run setup and updates the README to explain that configuration commands should be saved inconfig.ps1.Changes:
Start-Commanderfinds an empty config file.New-Commander*commands in an interactive session does not automatically persist them toconfig.ps1.Closes #1