- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1
π Integrate develop β staging (13 commits) #292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     Merged
            
            
          Conversation
  
    
      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
    
  
  
    
    - Remove unnecessary composables export from index.ts - Add proper default props to VPivottable component - Fix isolation between VuePivottable and VuePivottableUi components - Reduce bundle size by removing unused code Fixes #undefined - TypeError when using VuePivottable without aggregators π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Make aggregatorName, renderers, rendererName optional in DefaultPropsType - Add proper defaults in VPivottable component - Fix TSVExportRenderers to handle undefined aggregatorName - Resolve Vue warn messages for missing required props Fixes missing required props warnings when using VuePivottable π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Add changeset for patch release addressing component isolation and prop issues - Includes fixes for undefined errors and missing required prop warnings π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Apply sed command to decode %0A line breaks in PR creation - Ensure Recent Commits section displays properly with line breaks - Align formatting with PR update functionality π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Fix memory leak in VPivottableUi by implementing proper PivotData memoization - Replace inefficient watchEffect with controlled recreation based on structure changes - Add deep cleanup to break circular references between PivotData and aggregators - Fix renderer undefined error (Issue #269) by adding default TableRenderer - Add null safety check for renderer access - Optimize PivotData creation to only occur when essential properties change Fixes #269, #270 π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Enhanced aggregator cleanup to break all closure references - Added markRaw to prevent reactivity on large data arrays - Implemented component key cycling to prevent accumulation - Deep cleanup of all PivotData properties including function closures - Break circular references in row/col totals and allTotal aggregators Expected: Memory usage should stay below 50MB after 750 refreshes Previous: 466MB memory growth, now should be <50MB π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
**Root Cause Identified:** - pivotDataKey only checked dataLength, not actual data changes - Same length data (1000 records) resulted in no PivotData recreation - Old data accumulated without cleanup for 800+ refreshes **Fix:** - Include actual data reference in pivotDataKey computation - Now detects when new data array is generated (same length, different content) - Forces PivotData recreation and cleanup on each refresh **Expected Result:** Memory should reset to baseline (~43MB) on each refresh instead of accumulating π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
β¦umulation
**Root Cause Found:**
- JSON.stringify(dataReference) was creating massive string overhead (24MB β 1018MB)
- Component Key was fixed at 0, preventing component destruction/recreation
- Memory accumulated because same component instance reused indefinitely
**Solution:**
- Remove complex memoization logic that was causing string bloat
- Use simple computed(() => new PivotData(state)) for reactivity
- Force component recreation with :key="pivot-${refreshCount}"
- Each refresh destroys previous component and creates clean instance
- Clean up unused imports (shallowRef, watchEffect, onUnmounted)
**Expected Result:**
Memory should stay stable around baseline instead of accumulating
π€ Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <[email protected]>
    - Remove unnecessary test files and move to project root - Optimize useMaterializeInput with shallowRef for large data - Add proper cleanup in onUnmounted hooks - Use toRaw() in PivotData creation to reduce reactivity overhead - Remove unused usePivotModelHistory and useDraggableMemoryFix - Simplify main.ts to use App.vue directly - Remove deep watch to prevent performance issues
Fixed undefined SimpleApp reference to use App component. π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
π€ Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
fix: optimize memory usage and remove unnecessary code
  
    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.
  
    
  
    
π Integration from develop to staging
π Summary
π Recent Commits
π What happens next?
β‘ Notes
New commits: 13
π Recent Commits