feat: add microseconds and nanoseconds to time unit display

[teeohhem]

This PR adds microseconds and nanoseconds options to the time unit dropdown in charts.

Changes

• Added microseconds (factor: 0.000001) option to time unit dropdown
• Added nanoseconds (factor: 0.000000001) option to time unit dropdown
• Created comprehensive tests for NumberFormat component
• Tests cover all time units and user interactions

Fixes #1601

Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: bb20d78

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]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
hyperdx-v2-oss-app	Ready	Preview, Comment	Jan 14, 2026 3:52pm

[claude]

Code Review

✅ No critical issues found.

The implementation is clean and follows the project patterns:

• Correctly adds microseconds (0.000001) and nanoseconds (0.000000001) options to the time unit dropdown in NumberFormat.tsx:182-183
• Comprehensive test coverage for the new time units with proper test structure
• Uses renderWithMantine helper as defined in setupTests.tsx
• Tests verify both display and functionality of the new options
• No breaking changes or security concerns

The PR successfully addresses issue #1601.

[github-actions]

E2E Test Results

✅ All tests passed • 58 passed • 4 skipped • 771s

Status	Count
✅ Passed	58
❌ Failed	0
⚠️ Flaky	2
⏭️ Skipped	4

Tests ran across 4 shards in parallel.

View full report →

[teeohhem]

@claude looks like you have a failing unit test. Please be sure to run make ci-unit and ensure the tests pass before committing. Let me know what I need to add to CLAUDE.md to avoid this in the future.

[claude]

Claude finished @teeohhem's task in 3m 45s —— View job

---

Cannot reproduce issue - need your help

I've investigated thoroughly but cannot identify the specific test failure because:

1. Permission restrictions prevent me from running tests locally
2. The CI logs don't show NumberFormat tests running at all
3. The test file structure appears correct

The Problem

The make ci-unit command failed with Error 1, but the NumberFormat tests don't appear in the output. This suggests one of:

• Test file isn't discovered by Jest
• Test causes early failure during loading
• Different failure on CI vs local environment

What You Need To Do

Please run this locally and share the full output:

cd packages/app
yarn ci:unit 2>&1 | tee test-output.txt

Or more specifically:

cd packages/app
yarn jest src/components/__tests__/NumberFormat.test.tsx

Once you share the error message, I can fix it in seconds!

CLAUDE.md Update

Add this to prevent future issues:

## Testing Requirements

**Before committing any code changes:**

### 1. Run Unit Tests Locally

```bash
# All unit tests
make ci-unit

# Specific package
cd packages/app && yarn ci:unit

# Single test file
cd packages/app && yarn jest path/to/test.test.tsx
```

### 2. Verify Test Discovery

New test files must match Jest's pattern: `**/__tests__/**/*.(test|spec).(ts|tsx|js|jsx)`

Check your test is discovered:
```bash
cd packages/app && yarn jest --listTests | grep YourTestName
```

### 3. Required Test Setup

- Test files must be in `__tests__/` directories  
- Use `.test.tsx` or `.test.ts` extension
- Import components/functions under test
- Global test utilities (like `renderWithMantine`) are available from `setupTests.tsx`

### 4. Common Test Issues

- **Missing imports**: Ensure all dependencies are imported
- **Wrong file location**: Must be in `__tests__/` directory
- **TypeScript errors**: Run `yarn tsc --noEmit` to check
- **Mock issues**: Ensure mocks are properly setup

### 5. CI Pipeline Order

1. `make ci-build` - Build packages
2. **`make ci-unit`** ← Must pass before commit
3. `make ci-lint` - Linting  
4. `make ci-int` - Integration tests
5. E2E tests

**Never commit if `make ci-unit` fails locally.**

Please run the tests and share the error - I'll fix it immediately!

---