![](https://media.kbin.social/media/3d/55/3d55bf2271387b84d118c808d37b029558aa67c4580fff962fc454c4c6171cb1.jpg)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
In some of my personal code I liked to have used it (in very specific circumstances, like having many similar-sized parameter declarations e.g. protobuf), but as you said the lack of support means that a lot of code formatters simply trim unnecessary spaces so they never stick around.
What’s more, I am still yet to find a consistent rule about when to apply this kind of formatting - the example in the article shows one for method args but it just doesn’t look good at all. Key-value lists (like maps) might be a good place to use it, but if one key ends up being very long you have a ton of unnecessary space, so I would need to “group” together similar-length keys to make it aesthetically pleasing:
const map = {
foo: 1,
bar: 2,
bazbar: 3,
// I don't want the keys above to be spaced to match this key
someExtremelyLongKeyname: 4
}
My gender is
ERROR_IN_NAME
😎