Cull Feature Requests That Will Not Be Implemented

[alex-courtis]

nvim-tree is stable and (large) feature complete.

Future changes to nvim-tree are limited to:

• Bug fixes
• Quality of life improvements
• Feature parity for options such as floating
• API / Event additions

New features outside of the above will not be added. Users may be encouraged to develop features via API / custom actions.

Such feature requests should be declined e.g. #923

[alex-courtis]

Can I please ask for your assistance on this one @gegoune ?

[gegoune]

@alex-courtis What exactly needs to happen?

[alex-courtis]

We should go through older feature requests and close any that are large new features outside of the scope of nvim-tree. Merging #1666 first would be useful so that we can point the user to the roadmap.

I cherry picked an easy one #923 which requires understanding of the (code) structure of the directory. It could possibly one day be implemented by a user via API but doesn't belong in nvim-tree itself.

[alex-courtis]

I've published the roadmap, it can change.

I've been going through the least recently updated feature requests. It's slow and will take a while...

API and QOL tags have been added which map nicely to the roadmap along with Bug.

[alex-courtis]

Slowly going through. Using API and QOL to tag processed issues.

[alex-courtis]

Backlog is quite clean now.