{"version":"2.1.269","anchor":"output-style-change-now-requires-localsettings-and-warns-on","canonical_anchor":"output-style-change-now-requires-localsettings-and-warns-on","heading":"Output style change now requires localSettings and warns on redundant switch","tier":"notice","area":"Output Style","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/output-style-change-now-requires-localsettings-and-warns-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Output style change now requires localSettings and warns on redundant switch\n\nSwitching output style in \/config is now safer for shared sessions and won't let you reselect the current style\n\n**What**\n\nThe output-style picker in the `\/config` settings panel now behaves more carefully when changing styles:\n\n- If the session might not belong to its original owner, it checks that a requested custom style is actually valid before allowing the switch.\n\n- If you pick the style that's already active, it now just tells you so instead of doing anything.\n\n- If the capability needed to save the change locally (`localSettings`) isn't available, it now errors out clearly before trying to save, rather than failing partway through.\n\n**Why**\n\nThese changes prevent confusing failures: a shared or non-owner session can't be pointed at an invalid style, picking your current style no longer does pointless work, and a missing save capability is caught up front instead of causing a silent or partial failure.\n\n- Area: Output Style\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}