Bug Report: Invalid DefaultProfile returns wrong warning #3429

Closed
opened 2026-01-30 23:21:06 +00:00 by claunia · 1 comment
Owner

Originally created by @carlos-zamora on GitHub (Aug 15, 2019).

Environment

After PR #2422

If I change the defaultProfile to an invalid guid, I get "No profiles were found in your settings.".

Expected behavior

Something a bit more specific like "GUID is invalid"

Actual behavior

"No profiles were found in your settings."

Originally created by @carlos-zamora on GitHub (Aug 15, 2019). # Environment After PR #2422 If I change the defaultProfile to an invalid guid, I get "No profiles were found in your settings.". # Expected behavior Something a bit more specific like "GUID is invalid" # Actual behavior "No profiles were found in your settings."
Author
Owner

@zadjii-msft commented on GitHub (Aug 18, 2021):

You know, this was fixed when we started allowing names in the defaultProfile property. Now it just gives you

image

which makes sense

@zadjii-msft commented on GitHub (Aug 18, 2021): You know, this was fixed when we started allowing names in the `defaultProfile` property. Now it just gives you ![image](https://user-images.githubusercontent.com/18356694/129954046-7372385b-622b-4bf3-a10f-f5ca2c897d6a.png) which makes sense
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3429