You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps the spec will benefit by also specifying other type of dependencies:
Neovim providers: provider-python, provider-node, etc. This could allow future integration with the healthcheck module.
External programs: ripgrep, find, etc. Could also be integrated with the healthcheck module could check for installation by checking for certain executable names, checking version would be perhaps too complex.
Point 1 seems straightforward to do, point 2 is more complex and out of the control of neovim development, still wanted to put the idea out there.
The field description.author could be a nice addition, I can imagine filtering packages by tpope, etc.
The text was updated successfully, but these errors were encountered:
Do you want to split these into separate issues? I think 2 is already covered by #13, I'm not quite sure about 1, maybe an additional key under dependencies providers? (cc @ii14). I think 3 is a straightforward addition and could be PR'd (maybe a table with email? name?)
Excited to see the spec :)
Perhaps the spec will benefit by also specifying other type of dependencies:
Neovim providers: provider-python, provider-node, etc. This could allow future integration with the healthcheck module.
External programs: ripgrep, find, etc. Could also be integrated with the healthcheck module could check for installation by checking for certain executable names, checking version would be perhaps too complex.
Point 1 seems straightforward to do, point 2 is more complex and out of the control of neovim development, still wanted to put the idea out there.
description.author
could be a nice addition, I can imagine filtering packages by tpope, etc.The text was updated successfully, but these errors were encountered: