Enhanced Finder with item_type hints and specialized picker support#1754
Open
Aitai wants to merge 6 commits intoNeogitOrg:masterfrom
Open
Enhanced Finder with item_type hints and specialized picker support#1754Aitai wants to merge 6 commits intoNeogitOrg:masterfrom
Aitai wants to merge 6 commits intoNeogitOrg:masterfrom
Conversation
Wrap fzf-lua actions with vim.schedule() and improve processing functions to prevent race conditions that caused the range picker to close early.
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 PR implements the enhanced Finder architecture discussed in #1748, adding
item_typehints that enable specialized picker providers while maintaining fallback compatibility.Key changes:
item_typesupport to Finder (branch,commit,tag,any_ref,stash,file)This provides the hybrid UI approach discussed: common operations are discoverable while power-user scenarios (like diffing CHERRY_PICK_HEAD against a tag) are handled by the flexible Custom Range action using
any_refitem_type.Closes #1748