MEGATHREAD: Breaking settings changes in version 0.11!

[DHowett-MSFT]

BREAKING SETTINGS CHANGES IN 0.11

• BREAKING CHANGE We've deleted a lot of legacy settings handling (Remove a heap of legacy settings deserialization #5190)
  • Please see our blog post and our most recent status update for more information.
  • If you had settings hanging out in the globals dictionary, you'll want to move them out.
    • REMEDIATION: move everything from globals to the root of your settings file and delete the empty globals object.
    • Failure to do so will cause us to ignore your default profile, launch mode, etc., etc.
    • THIS INCLUDES defaultProfile
  • requestedTheme has been renamed to theme (Rename 'requestedTheme' to 'theme' #5265)
• profiles.json has been renamed to settings.json. This should be transparent to you as we'll rename it on first launch (rename profiles.json to settings.json, clean up the defaults #5199)
  • As a side effect, we'll finally stop resurrecting old pre-version-0.3 roaming profiles.
• If you don't specify a splitPane split mode, it'll default to automatic (Use an Automatic split for splitPane by default #5194)
• copy's original and poorly-understood trimWhitespace argument is now called singleLine to indicate that it will, in fact, copy text as a single line (Rename copy keybinding arg #5216)
• The default font for any profiles that don't specify a font is now Cascadia Mono (Set Cascadia Code as default font #5121)

---

Do your settings look like this?

{
    "globals": {
        "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
        "initialCols": 200,
        "initialRows": 65,
        "initialPosition": "0,0",
        "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502",
        "confirmCloseAllTabs": true,
        "keybindings": [
            ...
        ]
    },
    "profiles": {
        ...
    }
}

Then change them to look like this:

{
    "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
    "initialCols": 200,
    "initialRows": 65,
    "initialPosition": "0,0",
    "wordDelimiters" : " ()\"'-:,;<>~!@#$%^&*|+=[]{}~?\u2502",
    "confirmCloseAllTabs": true,
    "keybindings": [
        ...
    ],
    "profiles": {
        ...
    }
}

Or even better, make a backup of your settings file, and delete the contents entirely. We'll re-generate the file with some better formatting and more sane defaults, and you can copy the modifications you want back in.

[mlewand]

Out of curiosity, any reason why settings.json's global values weren't moved automatically to the root level after the upgrade? You migrate the config on multiple occasions which is good, but not this time.

I myself had this problem and got into #5489 even though I scanned changelog before the upgrade, but haven't picked up that I have actually to change something in my config 🙂

[bmarkovic]

If you had settings hanging out in the globals dictionary, you'll want to move them out.
Failure to do so will cause us to ignore your default profile, launch mode, etc., etc.
THIS INCLUDES defaultProfile

You might want to reword that from "move them out" as that really doesn't say nearly enough to anyone. Be specific:

...you will need to move them to the root object of the settings.json.

[DHowett-MSFT]

Bojan Markovic (@bmarkovic) that’s a great suggestion, thank you. I appreciate that you edited your comment.

[bmarkovic]

In my particular case this didn't restore functionality of keybindings, did something change about the format (or the JSON key name)?