1. Description
There are issues related to filter persistence and graph synchronization.
When applying two or more filters and reopening the webview, only one filter remains.
After refreshing with filters applied, the filters remain in the UI but are not applied to the graph.
2. Steps to Reproduce
Case 1 - Filter Persistence Issue
- Open Git Graph+
- Apply two or more filters
- Close the webview
- Reopen the webview
- Check the applied filters
Case 2 - Graph Synchronization Issue
- Open Git Graph+
- Apply one or more filters
- Verify that the graph is filtered correctly
- Refresh the page/webview
- Check the filter UI state and graph data
3. Expected Behavior
- All applied filters should persist after reopening the webview.
- After refreshing, both the filter UI state and graph data should remain synchronized, and the graph should still reflect the applied filters.
4. Actual Behavior
- After reopening the webview, only one filter remains while the others are removed.
- After refreshing, the filter UI remains selected but the graph is displayed in the unfiltered state.
5. Screenshots or Logs
Attach any screenshots or log output that may help diagnose the issue.
You can view executed Git command logs in the Activity Log tab.
6. Environment
- OS: (e.g., macOS 15.3, Windows 11, Ubuntu 24.04)
- VS Code version: (e.g., 1.96.0)
- Git Graph+ version: (e.g., 0.1.0)
- Git version: (e.g., 2.43.0)
- Node.js version (optional): (e.g., 20.11.0)
7. Additional Context
Provide any other relevant information.
- Whether the issue occurs only in a specific repository
- Whether submodules or worktrees are in use
- Approximate repository size (number of commits)
1. Description
There are issues related to filter persistence and graph synchronization.
When applying two or more filters and reopening the webview, only one filter remains.
After refreshing with filters applied, the filters remain in the UI but are not applied to the graph.
2. Steps to Reproduce
Case 1 - Filter Persistence Issue
Case 2 - Graph Synchronization Issue
3. Expected Behavior
4. Actual Behavior
5. Screenshots or Logs
Attach any screenshots or log output that may help diagnose the issue.
6. Environment
7. Additional Context
Provide any other relevant information.