WIP: Remove TaskHistory from extensionState, lazy fetch tasks using useTaskHistory #2226
+2,262
−88
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
|
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.
This is a heavily vibe-coded branch that I was working on in order to remove the task history metadata from the extension state. Currently, all of the metadata for the whole taskHistory is sent as part of the extension state.
The goal of this PR was to remove the task history from the extension state and lazily fetch just a subset of the events using a new set of messages and a new hook. It has only been minorly tested. It looks like there might be a bug in the favoriting system. It needs a lot of love and a lot of cleanup, but if you can find it useful at all, here it is.
related: #1612