Settings editor doesn't support settings with very long descriptions well like terminal.integrated.commandsToSkipShell

[lramos15]

This setting takes the cake for longest description at ~7000 characters. It is too long to fit in the settings UI and seems to be mostly listing defaults? Is there a reason those defaults aren't just actual defaults for the setting? For me to read the whole setting description I must click the "open default settings" link in the description and then scroll to find this setting in the list.

cc @rzhao271 for how settings UI handles descriptions which are too long.

[meganrogge]

The first two sections of the description are necessary IMO. Maybe we shouldn't list the default skipped commands though.

[Tyriar]

We need to document what settings are included.

Is there a reason those defaults aren't just actual defaults for the setting?

The default is [] and the user can set "setting" to add it to the list or "-setting" to remove it. If we actually made all those the defaults then any change to this setting would add 136 lines to your settings file and also not be forwards compatible when we change the default list, the last point meaning some commands in the terminal will break over time if the user has customized it.

If you have ideas on how to do this differently they're welcome, but we've already refined this setting so it's a UI problem imo.

[lramos15]

Can we link to a doc about this setting and all the defaults? We suggest to extension authors in our best practices not to make descriptions too long https://code.visualstudio.com/api/ux-guidelines/settings, but I know this isn't always possible like with the telemetry setting.

[Tyriar]

Isn't that just a worse experience though? We should support longer description if they happen to exist, not break when they hit some unknown threshold?