feat(tracing): add resourcesDir option to Tracing.startHar#40488
feat(tracing): add resourcesDir option to Tracing.startHar#40488dgozman merged 1 commit intomicrosoft:mainfrom
Conversation
When `content: 'attach'` is used with a non-zip HAR path, response bodies are now placed alongside the HAR file by default, and can be redirected to an explicit `resourcesDir` instead. Throws when combined with a `.zip` path. Refactors HAR export to a mode-based protocol matching tracing.stopChunk (`entries` for in-process, `archive` for remote), so resources can be written directly to user-provided paths in-process and reuse the existing harUnzip flow remotely. HarRecorder now uses SerializedFS.
Test results for "tests 1"4 flaky41489 passed, 847 skipped Merge workflow run. |
Test results for "MCP"7 failed 6814 passed, 927 skipped Merge workflow run. |
Summary
resourcesDiroption toTracing.startHarto redirect attached response bodies to a user-chosen directory; defaults to the HAR file's directory. Throws when combined with a.zipHAR path.entries/archive), mirroringtracing.stopChunkso resources can be written directly to user paths in-process and the existingharUnzipflow is used remotely.HarRecordertoSerializedFS.