Skip to content

Conversation

@themavik
Copy link

Summary

Fixes #1510

Root cause: When a number format (e.g., Percent) is applied to table columns that contain non-numeric values, formatNumber doesn't catch non-empty strings. numbro() then produces NaN.

The existing check !value && value !== 0 catches null, undefined, and NaN, but NOT non-empty strings (which are truthy and pass through to numbro()).

Changes

  • packages/app/src/utils.ts: Added typeof value !== 'number' || isNaN(value) guard that returns the raw value as a string instead of formatting it.

Risk Assessment

Low - Only adds a guard for an edge case. Numeric values are formatted exactly as before.

When table columns contain non-numeric values (strings, etc.)
and a number format like Percent is applied, the formatting
produces NaN because `numbro()` can't parse strings. The
existing falsy check (`!value && value !== 0`) doesn't catch
non-empty strings since they're truthy.

Adds a `typeof` and `isNaN` guard to return the raw value
as-is when it's not actually numeric.

Fixes hyperdxio#1510
@changeset-bot
Copy link

changeset-bot bot commented Feb 10, 2026

⚠️ No Changeset found

Latest commit: 70dd220

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Feb 10, 2026

@themavik is attempting to deploy a commit to the HyperDX Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

1 participant