Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(editing-support): add mini-operators plugin #857

Merged
merged 3 commits into from
Apr 12, 2024

fix(mini-operators): correctly implement `keys` lazy loading

9f17c9b
Select commit
Loading
Failed to load commit list.
Merged

feat(editing-support): add mini-operators plugin #857

fix(mini-operators): correctly implement `keys` lazy loading
9f17c9b
Select commit
Loading
Failed to load commit list.
Task list completed / task-list-completed succeeded Apr 12, 2024 in 0s

3 / 3 tasks completed

All tasks have been completed

Details

Required Tasks

Task Status
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin Incomplete
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error Incomplete
Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above Completed
README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url) Completed
Proper usage of opts table rather than setting things up with the config function. Completed
I think overriding the neo-tree default is a no-go. @AstroNvim/astrocommunity-maintainers Any ideas? Incomplete
Similar to other reviews: Lets use the same method for mappings as we do most of the other plugins. Incomplete