Not having a settings file is a legitimate state (in fact, the most likely state on a new system).

Add a test(s) that ensures proper handling when the settings file does not exist.

Today a settings file is required in order to use this feature (experimentalFeature > dsc3 = true).

For instance, if we don't have a settings.json file and we do:

'{}' | winget dscv3 user-settings-file --set

or

winget dscv3 user-settings-file --get

We get:

This feature is a work in progress, and may be changed dramatically or removed altogether in the future. To enable it, edit your settings ('winget settings') to include the experimental feature: 'dsc3'

I will consider a way to handle this logic with test hooks but I will handle that part in a separate PR.

• DSCv3 user settings file enhancements #5425