Issue Summary

When creating a chart using Charty from a Confluence table that contains mostly text, Charty is still able to select certain columns as numeric measures. If those columns contain non-numeric or mixed text values, the chart renders with NaN values instead of:

• rejecting the invalid metric selection, or

• displaying a clear validation/error message.

Text columns should be allowed as dimensions/labels, but when a column is used as a metric, the product should either:

• enforce that it is numeric, or

• handle non-numeric cells gracefully and never surface raw NaN to the end user.

This is a poor error-handling / validation bug in Charty’s data interpretation.

Steps to Reproduce

1. Use Charty to create a chart from a table like attached

1. Select the Value column as the metric / Y-axis.

1. Generate the chart.

Expected Results

One of the following:

1. Validation / Blocking behavior

• • When a column is selected as a metric, Charty validates that the values are numeric.

1. Graceful handling behavior

• • Charty silently ignores non-numeric rows and uses only rows that can be parsed as numbers.

• • The chart displays valid numeric values only, and never surfaces NaN in the user-facing UI.

In all cases, NaN should not appear in the chart UI.

Actual Results

• Chart renders but shows NaN in place of numeric values.

• No clear validation or user-friendly error message is presented.

• End user sees raw NaN, which is confusing and looks broken.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available