[shayansadeghieh]

Uses the browser’s Performance API (performance.now() and performance.measure()) to record User Timing entries for expanding a parent row in the Nodes tab. Expansion latency can be inspected in DevTools or collected through PerformanceObserver by benchmarks and telemetry integrations.

flyteconsole.node.expand measures from the expand-arrow click until React commits the expanded child rows. Each entry includes detail.scopedId and detail.executionId (project, domain, name). The boundary is the row commit; it does not wait for browser paint or background requests.

Initial rendering, collapse, and subsequent re-renders do not emit measurements. A newer toggle replaces or cancels the pending measurement. Unsupported timing APIs are ignored, and no reporting dependency or network requests are added.

After expanding a node, inspect the measurements with:

performance.getEntriesByName('flyteconsole.node.expand');

Validation:

• 10 focused table tests pass, covering click-to-commit timing, metadata, duplicate suppression, collapse/re-expansion, and unsupported APIs.
• Targeted ESLint and Prettier checks pass (two existing lint warnings).
• Built a docker image and manually confirmed expansion measurements in Chrome (see attached video)

[welcome]

Congrats on merging your first pull request! 🎉

[flyte-bot]

🎉 This PR is included in version 1.23.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀