Table allows configuration of number column type

[nate-ni]

😯 Problem to Solve

A user needs to display numeric values to the user. These values may be integer or decimal based numbers.

The end user would like to be able to sort, filter, etc. based on these values.
Note: This feature would not provide that direct functionality but is a consideration for this feature.

💁 Proposed Solution

The user should be able to provide simple, supported, configurations easily.

Open Questions

Question	Initial Recommendation	Resolved	Decision
Which formatting options do we need to provide?	Integer and Decimal	No
Should we provide config for prefix? (e.g. currency symbols)	No	No
Should we provide config for prefix or suffix? (e.g. static string for units)	Yes	No
How should we provide alignment?	Always right-align content	No
Which width modes should we support?	Both fixed pixel width and fractional width	No

Other Considerations

Supporting the users local for number formatting
More info: Intl.NumberFormat - JavaScript | MDN

References/Prior Art

jQuery Grid Cells Formatting

📋 Tasks

Preview Give feedback

1. Visual Design for basic table content types #887
   UX-Deprecated +1
   
2. HLD brainstorming - Formatted text table columns #1054
   +0
3. Formatted text table columns HLD and component naming conventions #1224
   +0
4. Create base classes for text columns
5. Define API for numeric formatting
6. Define API for text alignment
7. Create custom elements for number column with basic API and default numeric formatting
8. Unit tests for formatting number edge cases (Inf, NaN, etc)
9. Add API to configure integer numeric formatting
10. Add API to configure decimal numeric formatting
11. Provide locale setting on nimble-theme-provider #1293
    enhancement needs investigation +2
    
12. Respect Nimble locale token for numeric formatting
13. Unit tests for invalid state with bad formatting configuration
14. Add API to configure text alignment
15. Angular integration
16. Blazor integration

[jattasNI]

I was curious about what kind of numeric formatting options we need. Here are the use cases I found in SLE that use either a number column type or a custom format function:

1. data table grid includes integer counts with default formatting
2. executions grid converts a numeric enum to a user-visible string. I think we'd rather make this a dedicated enum column type
3. test results grid formats elapsed time as "12 s" or "13 m, 12 s". I think we'd rather make this a dedicated elapsed time column type, possibly leveraging upcoming browser APIs like temporal
4. files grid formats file sizes using units like bytes, KB, MB, etc. I think we'd make this a dedicated custom column type.
5. wafer classification has lots of numeric columns but I believe they're all integer counts

Other use cases include formatting dates, times, icons, arbitrary custom columns, etc are covered by other work items.

Initial conclusion: It might be possible to keep the number column type extremely simple to start with by using default numeric formatting and not allowing units. Posting this to capture notes and hear hot takes, but we can hash out in detail in an HLD.

[jattasNI]

The SLS Tag grid shows tag values with numeric formatting that is not end-user configurable. Some of these use cases also might require a custom column because tags can be various non-numeric data types.