How Are The URL and Maintainers Documentation Parsed?

[jgarte]

Hi,

How Are The URL and Maintainers Documentation Parsed?

I'd like to fix some that are not being parsed. Is this from the nixpkgs side? 🦆

[traxys]

Do you have an example of a missing one? They are parsed through the meta.nixvimInfo and meta.maintainers nix options, most of the plugins using mkNeovimPlugin are automatically populated, but some plugins are older and don't use those helpers

[jgarte]

TIL 🦆

[traxys]

You can still add the URL to the documentation by specifying the meta.nixvimInfo value we do that in plugins/lsp/language-servers/_mk-lsp.nix for example:

  meta.nixvimInfo = {
    # TODO: description
    url = args.url or opt.package.default.meta.homepage or null;
    path = [
      "plugins"
      "lsp"
      "servers"
      name
    ];
  };

[jgarte]

TIL

[jgarte]

@traxys Should we do that until upstream resolves the propagation of that documentation?

[traxys]

I'm not sure I understand what upstream you are talking about? Those links are generated solely by nixvim, so if we want to change something about them it must be done in nixvim.
I don't think anyone would have an issue if you open a PR to add the project URL to the plugins which don't use mkNeovimPlugin