nvim-treesitter / nvim-treesitter/nvim-treesitter-textobjects
Built in textobjects table is hard to read
Nobody has claimed this yet.
- Dominant language
- Tree-sitter Query
- Stars
- 2.8k
- Forks
- 271
- Avg merge
- 8d 8h
- Merged PRs (30d)
- 1
Description
I think this table about which features work for which languages is hard to extract information from.
I think it would be more helpful to show a list, for each language, of which text objects are known to work. This way a user, interested in using this tool for a particular language could just peruse that list instead of scrolling up and down and tracking lines on the page.
Thanks for the cool work! This is great stuff.
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 with the linked “Built-in textobjects” table in the project documentation and inventory its language and text-object entries. Reorganize the information into a per-language list while preserving the documented support, then review the rendered page to confirm users can find each language’s supported text objects.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100