- Issue created by @Anybody
- π©πͺGermany Anybody Porta Westfalica
@maintainers: Could you maybe explain a bit how the module handles numeric values and if (or why not) raw values are used?
Currently this seems unusable for non-default number formattings used in the view output, as described in the example.We'd like to help, but it would be great to have a better starting point on how and where this should be fixed and which impediments you see. Thank you!
- πΊπΈUnited States tr Cascadia
I was not involved in writing that code and I don't know what the original intent was for how to handle number formatting. I would have to first try to reproduce this problem then figure out what to do about it. Usually, formatting numbers would be something done as late as possible, because this is essentially just theming/presentation and could differ on a per-user/per-page/per-view basis.
Since you already have a site set up that uses a different number format, you are in a better position to create a test case that demonstrates the problem. That is the first step in finding a solution. If you can do that, it would go a long way towards getting this fixed.
- πΊπΈUnited States mortona2k Seattle
MR36 fixes the issues with number formatting with decimals/commas: https://www.drupal.org/project/views_aggregator/issues/3482129 π Crashes with Drupal\views_aggregator\Plugin\views\style\Table::setAggregatedGroupValues(): Argument #3 ($group_aggregation_results) must be of type int, string given Active
To test, I added a decimal field to the article content type in the standard install profile, and generated content with devel generate.
Then I created a view that lists article titles and the decimal field, formatted with views aggregator.
Group sum:
Column sum:
There are a handful of options to test, like enabling prefix/suffix, which is configured in the field settings.