Does packer support nested lists of plugins? #1026
danielo515
started this conversation in
General
Replies: 2 comments 2 replies
-
Yes packer does support nested lists of plugins. A plugin use {
{ config = function() end, "user/repo" }, -- invalid
}
-- All valid
use {
"user/repo", -- single
{
"user/repo", -- list of singles
"user/repo",
},
{ "user/repo" }, -- complex with additional keys
{
{ "user/repo" }, -- list of complex with additional keys
{ "user/repo" },
{ "user/repo" },
},
}
This is the same for the |
Beta Was this translation helpful? Give feedback.
2 replies
-
Awesome! Thank you so much for the answers.
…On Tue, Aug 23, 2022 at 3:47 PM EdenEast ***@***.***> wrote:
There is no restriction on the level of nesting. When nesting you have to
make sure that the each nesting level is a list.
—
Reply to this email directly, view it on GitHub
<#1026 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARKJWJ2IHG2KJVAQ4GZ7XDV2TI7PANCNFSM57G3BZGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
---
https://danielorodriguez.com
|
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
-
Hello, and as always, thanks again for packer.
Today I realized that, under my main list of plugins, I have some nested lists of plugins, and I am not sure if packer is able to pick them? Maybe it is some side effect from a flatten call, or maybe it is an intended design decission? The thing is that I don't get any error, and everything seems to work, but I didn't saw any reference to poviding nested list of plugins.
To put it in concrete terms, this is what I am talking about
Beta Was this translation helpful? Give feedback.
All reactions