nvim-treesitter / nvim-treesitter/nvim-treesitter-textobjects
Does it make sense to treat elements in a tuple/array literal as part of the @parameter object?
Open
A pull request for this has already been merged.
- #767 by @kiyoon — merged
enhancement
- Dominant language
- Tree-sitter Query
- Stars
- 2.8k
- Forks
- 271
- Avg merge
- 8d 8h
- Merged PRs (30d)
- 1
Description
They are syntactically similar, and semantically not that different. I think there should be a text object for entries in lists/tuples/dictionaries, but the question is whether it should be in the parameter text object or another (@entry? @element)
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
Review the issue discussion and merged pull request #767 first to determine the current state of this proposal. Any remaining work must settle whether list, tuple, and dictionary entries belong to @parameter or use a separate text object such as @entry or @element, with the chosen behavior implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100