nvim-lua/wishlist

JetBrains Rider like features

Open

#33 opened on Oct 15, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees) (0 forks)github user discovery
help wantedidea

Repository metrics

Stars
 (249 stars)
PR merge metrics
 (PR metrics pending)

Description

What? So I have made a list based on stuff i really enjoyed seeing in Rider:

  • Context Action Menu via Alt + Enter

    • Could be a really useful feature first show code actions and then user mapped actions such as renaming etc instead of remembering a command/10 million keybinds, with the ability to search mapped actions

  • Generate variable name suggestions if type is not a primitive type

  • Move function/class/struct/etc to another file using treesitter(?)

  • Alt + {button} for quick action

    • When cursor hovering on symbol function/class/variable do quick actions such as: quick delete/rename/move up/down and could be used for many other symbol specific actions

  • symbol rearranging using something like CTRL(or ALT when GUI) + Up/Down/Left/Right when cursor hovering symbol

Why? JetBrains rider and or more generally JetBrains IDEs have some of the best programmer-language supporting features which really does boost the efficiency of the programmer using whatever the programmer is using, and could be somewhat "easily" implemented considering we have LSPs and tree-sitter

Potential existing implementations: Not that I could find.

Potential pitfalls: No idea to be honest

Contributor guide

Research direction
Start by implementing one specific feature, such as the context action menu via Alt+Enter. Research Neovim's built in LSP code actions and vim.ui.select to create a popup. Look at existing plugins like 'nvim lspcompletion' for reference.
Tech stack
lua
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
NeovimLuaLSPtree sitter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15