-
-
Notifications
You must be signed in to change notification settings - Fork 802
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
EnablePromptStatus should not affect Get-GitStatus #475
Comments
The Would it work for you if we added |
Yeah, that would certainly get the job done. Thank you! |
Did you start on this? |
I looked at it and was starting to come to the same conclusion you had - nervous about the change. Unfortunately, it affects all the new |
That said, I'm OK punting on this for the first beta. |
Let's just do this. It can easily target v0.x and be pulled into v1. |
I have a fix for this. Waiting on PR #533. |
Fix #475 add -Force param to Get-GitStatus
This is fixed in the upcoming 1.0.0-beta2. |
System Details
Issue Description
I have a use case which needs to disable the command prompt status while still using the Get-GitStatus function. Disabling the prompt is easy: set GitPromptSettings.EnablePromptStatus to false. But, Get-GitStatus also checks that setting, making the command ineffective.
If this coupling is not intentional, I propose adding a separate setting, such as EnableGetStatus or EnableGetGitStatus, so that these pieces of functionality can be managed separately.
If it is intentional, a simple enough workaround is wrapping Get-GitStatus with a function that temporarily changes the GitPromptSettings.
The text was updated successfully, but these errors were encountered: