Number format for tables should not be applied for non-numeric values (grouping keys) #1510

Activity

1. pulpdrew commented on Dec 20, 2025

   

   pulpdrew

   on Dec 20, 2025

   Contributor

   More actions

   Thanks for raising this issue @kirik. This appears to impact group-by keys with aliases and/or with map accesses, due to the usage of arrayElement(...) breaking the matching logic in #1121.

   We can take a look at making that fix more robust.

   ❤️React with ❤️1Reacted by Kirill
2. linear

   added

   bugSomething isn't workingSomething isn't working

   on Dec 20, 2025
3. kodiakhq

   closed this as completedin #1721on Feb 26, 2026
4. kodiakhq

   added a commit that references this issue on Feb 26, 2026

   fix: guard formatNumber against non-numeric values (#1721)

   ...

   This issue will close once commit 3797e65 is merged into the 'main' branch.

   3797e65
5. karl-power commented on Feb 26, 2026

   

   karl-power

   on Feb 26, 2026

   Last edited by karl-power

   Contributor

   More actions

   Reopening as while the attached PR might hide the issue, it does not address the root cause. See comment in PR for details.
6. karl-power

   reopened this on Feb 26, 2026
7. knudtty

   added a commit that references this issue on Apr 16, 2026

   fix: guard formatNumber against non-numeric values (#1721)

   ...

   This issue will close once commit dcdb695 is merged into the 'main' branch.

   dcdb695
8. pulpdrew commented on Jun 4, 2026

   

   pulpdrew

   on Jun 4, 2026

   Contributor

   More actions

   This seems to have been fixed by #1721, #2149, and #2174
9. pulpdrew

   closed this as completedon Jun 4, 2026