nvim-treesitter / nvim-treesitter/nvim-treesitter-textobjects
Transition to `main` branch
Nobody has claimed this yet.
- Dominant language
- Tree-sitter Query
- Stars
- 2.8k
- Forks
- 271
- Avg merge
- 8d 8h
- Merged PRs (30d)
- 1
Description
Nvim-treesitter is in the process of graduating the main branch, so nvim-treesitter-textobjects needs to follow suit.
[!WARNING]
Themainbranches are incompatible rewrites, and you cannot mix-and-match! If you do not want to deal with breaking changes, pin bothnvim-treesitterandnvim-treesitter-textobjectsto the respectivemasterbranch, which will remain available (even if no longer updated).
Roadmap:
- Port testing infrastructure from
nvim-treesitter(#776 - Freeze the
masterbranch - Cherry-pick(!) query updates from
masterbranch - fix test failures (related to Neovim nightly changes?)
- switch the default branch to
main - Set up (buffer-local) mappings through
setup() - Update documentation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's setup() entry point and current documentation, then compare the remaining checklist items with the main-branch behavior. Done means buffer-local mappings are configured through setup() and the documentation is updated; verify with the ported testing infrastructure.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100