feat: add option to control behavior when rejecting new file diffs #114
+119
−2
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.
Add option to control behavior when rejecting new file diffs
This PR adds a new configuration option
on_new_file_reject
that controls what happens when a user rejects a diff for a new file:keep_empty
(default): Leaves the empty buffer in placeclose_window
: Closes the placeholder split windowPreviously, when rejecting a new file diff, the plugin would always try to delete the original buffer. This could cause issues when the buffer was reused from an existing empty buffer, leading to potential crashes when attempting to reopen a diff.
The PR includes:
config.lua
with validationtypes.lua
diff.lua
to track whether the original buffer was created by the pluginThis change improves stability when working with new files and gives users more control over the UI behavior.