jcberquist
commented
7 years ago The issue here (and I am probably going to say some things here you already know) is that ST merges the default settings with the user settings at the top level, and not recursively. If you leave a key out of a nested object, then that setting will be gone, rather than falling back to the setting in the default settings file. So in the situation you describe the formatting command cannot find the after_comma_spacing setting. Rather than throw an error (maybe that would be better?) I chose to treat it as if you had set it to compact. I checked and I did document the situation in the default settings file as I note there:
// IMPORTANT: it merges at the top key level, and not recursively, so when specifying a
// settings object in your user settings file, you must include all of its propertiesand with regard to white space settings when formatting delimited scopes in particular:
// if the `delimited_scopes` command is run, due to how it computes whether to render inline or multiline, the
// whitespace settings cannot be ignored, and anything other than `spaced` will be treated as `compact`Now I suspect you already knew that, and I get that it might be preferable to fall back to the nested setting in the default settings, so maybe it is worth changing that around. But I do regard the situation of specifying a nested object without specifying all of its keys as "unsupported", so my first preference would be that you include all of the nested object keys. (Particularly since not all of the default white space settings are set the same way.)
mjhagen
When I omit
after_comma_spacingfrom any of the top level keys in my owncfml_format.sublime-settingsfile it defaults tocompact, I would think that it would default to the value it has in the packagecfml_format.sublime-settingsfile (which isspaced).