feat: protect file operations from pruning #230
Merged
+162
−1
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
merge dev into master
merge dev into master
Introduced a new configuration option `protectedFilePatterns` to the plugin, allowing users to specify glob patterns that protect certain file operations from being pruned. Updated relevant functions to check against these patterns before executing pruning actions.
Contributor
Author
|
@Tarquinen would this work for you? |
Collaborator
|
This looks great, sorry for the delay finally got time to check this out |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
protectedFilePatterns(glob patterns) to prevent pruning of tool calls with matchingparameters.filePath.<prunable-tools>,discard,extract).Fixes #21
Test plan
npm run typechecknpm test