Repository navigation
fix: address #1180, #1181 - #1207
Merged
Merged
Conversation
|
@Helix-xi Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fix: address #1180, #1181
What was solved
#1180 — Implement debug mode with verbose output
Add a debug mode with configurable verbosity levels, verbose operation logging, debug breakpoints, debug utilities, an interactive debug console, and debug analytics. The issue is broad and touches cross-cutting SDK concerns; a focused implementation should introduce a small debug module (levels, logger, breakpoints, utilities, console, analytics) and wire it into the existing SDK surface without refactoring unrelated code.
Addressed:
#1181 — Add profiling tools for performance analysis
Add a profiling toolkit to the SDK covering CPU profiling, memory profiling, flame graph generation, call tracing, profile export, and a profile viewer. The repo already has an examples/profile-session.ts hinting at a profiling surface, so the contribution should introduce a focused profiling module (likely under src/) plus a viewer/export helper, keeping scope to profiling only and not touching unrelated SDK features.
Addressed:
Changes
src/analyticsTracking.ts(modify)src/__tests__/sdkFeatures.test.ts(modify)src/profileViewer.ts(create)Approach
Issues
Closes #1180
Closes #1181