Uh oh!
There was an error while loading. Please reload this page.
Fix PowerShell profile casing - #303
Conversation
Jason Helmick (theJasonHelmick)
commented
Apr 3, 2023
Justin Grote (@JustinGrote) - thank you for this pr. Hey Justin - bhavanakonchada and I are reviewing the change - Justin, can you change the conditional to the following logic? If lowercase only exists - do nothing |
bhavanakonchada
commented
Apr 3, 2023
Adding to what Jason Helmick (@theJasonHelmick) said, we need this change to avoid any disruption for existing customers as a lot could be riding on this path. |
Justin Grote (JustinGrote)
commented
Apr 3, 2023
bhavanakonchadaJason Helmick (@theJasonHelmick) I added migration logic as appropriate and tried to handle all possible edge cases, I did not do this transparently as users should be informed what is going on. |
Jason Helmick (theJasonHelmick)
commented
Apr 10, 2023
Thank you Justin Grote (@JustinGrote) - much appreciated. Will review with bhavanakonchada with the plan to accept the PR after testing. |
Jason Helmick (theJasonHelmick)
commented
Sep 27, 2023
I've delayed the review and merge of the PR to October 2023 post feature release for Ephemeral and UX2. Thank you for this fix - looking forward to have it included soon. WE may need to adjust the code for our own purposes, but the credit goes to you Justin Grote (@JustinGrote) for the catch and code. Thank you! |
The powershell profile folders have incorrect casing (PowerShell instead of powershell) to the powershell default, and cause problems with scripts that interact with them. This PR fixes the casing.
Related Discussion: #302