VSCode detected that I do not have an existing profile even though it is there. I think it is because my profile's name is zTrial and favorites saved it as ztrial.
I refreshed my workspace and I cannot re-create the error again. weird...
I tried again and saw that when the defaultProfile is loaded it changes all text to small caps then the error happens.
So, would a solution be to just take the profile name as is?
There is a similar issue that talks about profile names and how the some things don't care if it's all caps or not.
https://github.com/zowe/zowe-cli/issues/551
So, would a solution be to just take the profile name as is?
maybe. My issue now is that I can name all my profiles like Ztrial, zTrial, ztRial or zTrIaL and all of them will be different profiles 馃槅
Maybe, when working with profiles, always compare profile.name.toUpperCase() or .toLowerCase(), even if we show the user something else (ie. we show them zTrial, but we compare ZTRIAL).
I tried the addFavorites function and it adds a favorite with the correctly-capitalized name. Perhaps this is an old bug now. Because with the new delete profile functionality, all persistent values with the profile's name are also deleted, and you can't edit the connection name through VSCode. So there is no way for the wrong profile name to get stuck in the persistent array.
You could still get the bug if you edited the settings.json file directly.
So can we consider this issue closed, or should it remain open because of the possibility of editing in the settings.json directly instance?
I would consider it closed because if someone chsnges settings.json directly, they will see the error message (the error is handled) but maybe @jellypuno has a more comprehensive solution idk
"I don't even have a pla" 馃槅
You can close it. You are not allowed to have the same name with different cases anyway so this is fine. 馃槈
@katelynienaber But what is PR #790 ?
Well it tells you in the PR XD That is related to this comment