- 🇺🇸United States xjm
I don't think that's correct actually -- 11.2.x is the current production branch. This change would never be backported to a patch release.
- 🇺🇸United States xjm
Thanks everyone for working on this issue!
The first question I ask myself when I review an issue is, "Should this change even be made in the first place?" For core, we additionally ask, "Does this belong in core?"
Unfortunately, every additional element added to the user interface actually decreases usability. During the Views in Drupal Core Initiative, we went through a massive effort with the Usability topic maintainers at the time to remove as many form elements and descriptions from the user interface as possible. So, based on that alone, I'm hesitant to add any small configuration elements to the core Views schemata. Views is, after all, highly extensible, so elements can also be added in contrib.
Furthermore, the separator used in numbers is actually dependent on the language used, so configuring this independently of the site language, config translation, and user's individual translation is somewhat against pattern.
As a Views subsystem maintainer, I'm going to say this feature won't be added to Views in core, and can instead be implemented in contrib.
Since folks have put so much time into this issue over the years, I'm saving the issue credits according to the core issue credit guidelines → . ( Wontfixed issues receive credit now too ✨ Grant credit for all closed issues, not just fixed issues Active .)
Thanks everyone for your contributions!