If I've already defined a plugin spec with a name
, can I list that name as a dependency in another plugin spec?
#42
Answered
by
folke
heygarrett
asked this question in
Q&A
-
If I have: return {
"jose-elias-alvarez/null-ls.nvim",
name = "null-ls",
dependencies = {
...
},
config = function()
...
end,
} Can I then to do this? return {
"jayp0521/mason-null-ls.nvim",
dependencies = "null-ls",
config = function()
...
end,
} |
Beta Was this translation helpful? Give feedback.
Answered by
folke
Dec 20, 2022
Replies: 2 comments 1 reply
-
No, you need to have the full name in the dep. But what is even better, is that you don't need to specify null-ls as a dep for mason-null-ls at all. It should all still work as expected |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
heygarrett
-
Hello, maybe I have a problem in understanding the basics of lazy, but please check the link I am sending (it is about enabling Null-ls after running nvim) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No, you need to have the full name in the dep.
But what is even better, is that you don't need to specify null-ls as a dep for mason-null-ls at all. It should all still work as expected