nushell / nushell/tree-sitter-nu
Pipeline
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 180
- Forks
- 38
- Avg merge
- 12m
- Merged PRs (30d)
- 1
Description
while working on #117 I noticed that the current pipeline didn't prevent me from breaking things. In that case, neovim crashed in certain circumstances. So I tried to reproduce that in the pipeline, but couldn't really setup something sensible.
I got some hints about what to consider and where to find some docs in this comment.
Currently, our pipeline does
- checkout the parser
- install npm and treesitter
- lint, using
prettier - run tests via
tree-sitter test
If we decide to keep queries within queries/nu/*.scm and an nvim plugin via plugin/init.lua, we might want to:
- assert that queries are valid with the current grammar
- try to highlight a
.nufile in neovim, testingplugin/init.lua. Or at least open a*.nufile in neovim.
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 current pipeline and the discussion linked from pull request #117. Inspect queries/nu/*.scm and plugin/init.lua, then determine whether the pipeline should validate queries, open a .nu file in Neovim, or both. Done means the chosen checks run reliably and catch the reported breakage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim
- Domain
- ci-cd, devtools, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100