vimPlugins.render-markdown-nvim: add nvim-treesitter dependency

[GaetanLepage]

Description of changes

From their README
it seems that treesitter is required.
The rest look like optional dependencies.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[GaetanLepage]

Result of nixpkgs-review pr 343557 run on x86_64-linux 1

2 packages built:

• vimPlugins.render-markdown-nvim
• vimPluginsUpdater

[teto]

it should not be too hard to test the plugin. add the dependencies into RTP (since nixpkgs infra doesn't do that yet) , open a markdown and see if if neovim errors out. like
nvim -c"set rtp+=${vimPlugins.nvim-treesitter}" -c "${render-markdown-nvim}" "PreviewMarkdown" -es +quitall!

Some tests are visible for reference at
#343769

[PerchunPak]

nvimRequireCheck = "render-markdown"?

[GaetanLepage]

Sure ! Done.

[PerchunPak]

LGTM

[GaetanLepage]

it should not be too hard to test the plugin. add the dependencies into RTP (since nixpkgs infra doesn't do that yet) , open a markdown and see if if neovim errors out.

This didn't make it to the PR in the end.
Do you have a plugin examples where those tests are used already ?

[mrcjkb]

This is one of those cases where the plugin doesn't actually depend on nvim-treesitter, but it requires one or multiple parsers to be installed.

In such cases, adding nvim-treesitter as a dependency won't make the plugin work out of the box. Users will still have to specify nvim-treesitter.withPlugins ...
There's no need to add nvim-treesitter as a dependency if the plugin doesn't actually try to require one of its (legacy) modules.

[GaetanLepage]

This is one of those cases where the plugin doesn't actually depend on nvim-treesitter, but it requires one or multiple parsers to be installed.

In such cases, adding nvim-treesitter as a dependency won't make the plugin work out of the box. Users will still have to specify nvim-treesitter.withPlugins ... There's no need to add nvim-treesitter as a dependency if the plugin doesn't actually try to require one of its (legacy) modules.

Right, I forgot about this. I will revert it to prevent such noise from remaining in the code base.