Unable to build parser on Windows

[clason]

8ed571a introduced new tests, which include a symlink -- which are not supported by Windows by default. This means nvim-treesitter will fail to extract the tarball and hence install the parser.

[clason]

(For large outside corpus tests, it's better to keep them in external repos and clone/download them as part of the tests; see other parsers for examples. Forcing every user to download ~200 Mb of corpus files to install the parser is... less than great.)

[gmlarumbe]

Fixed in 89d4b39

Feel free to reopen in case it did not work, I could not test it under Windows.

(For large outside corpus tests, it's better to keep them in external repos and clone/download them as part of the tests; see other parsers for examples. Forcing every user to download ~200 Mb of corpus files to install the parser is... less than great.)

That is a nice suggestion. I will probably move the tests to a submodule in subsequent commits.

[clason]

Make sure these are not included when downloading a commit (or release) tar.gz from github (which is what nvim-treesitter does). Right now, that tar is 14Mb, which is not much by itself -- but it has to be downloaded on every CI run for every PR, not just in nvim-treesitter but also other projects which use it as a "crater test" for the collection of parsers and queries it tracks.

[gmlarumbe]

The release process makes use of the tree-sitter workflows: https://github.com/tree-sitter/workflows

The release.yml workflow in turn makes use of https://github.com/actions/checkout without setting the submodules option. I assume that it will only package what it clones but I will need to wait till next release to confirm it.

[clason]

No, we don't (can't) use these. We are using the builtin Github archive download endpoint, which packages the repo as-is (hopefully).

[gmlarumbe]

Test files moved to submodule #48

[clason]

Archive is 3Mb, that's much more manageable 👍