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
.nu file in neovim, testing plugin/init.lua. Or at least open a *.nu file in neovim.
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
prettiertree-sitter testIf we decide to keep queries within
queries/nu/*.scmand an nvim plugin viaplugin/init.lua, we might want to:.nufile in neovim, testingplugin/init.lua. Or at least open a*.nufile in neovim.