forked from bvaughn/scheduling-profiler-prototype
-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
importance: 1 - must haveMust be implemented for the issue's phase to be completeMust be implemented for the issue's phase to be completephase: 1 - MVPTasks that get us to our initial MVPTasks that get us to our initial MVPurgency: 1 - within 2 dayswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing codework type: investigationA task that primarily involves digging into a particular problemA task that primarily involves digging into a particular problem
Description
Steps
- Complete Add user timing marks for scheduling profiler tool react#11 to an extent where we can export performance profiles containing marks
- Define new V2 data types to support new marks
- Create preprocessDataV2 to support new data types and new marks
Acceptance criteria
- A new
ReactProfilerDataV2and other V2 types should be created to support the new profiling marks. - preprocessDataV2 should transform a raw profiling JSON into a correct
ReactProfilerDataV2 - No parsing errors in console on page load
- Neat code, possibly tested (blocked by Set up testing infrastructure #14)
Metadata
Metadata
Assignees
Labels
importance: 1 - must haveMust be implemented for the issue's phase to be completeMust be implemented for the issue's phase to be completephase: 1 - MVPTasks that get us to our initial MVPTasks that get us to our initial MVPurgency: 1 - within 2 dayswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing codework type: investigationA task that primarily involves digging into a particular problemA task that primarily involves digging into a particular problem