How is the merge order of plugin specs determined? Is it deterministic?

[cangermueller]

Hi,

I have plugin specs of this kind:

require("lazy").setup(
  {
    {
       url = "some/url/foo",
       import = "foo.default",
    },
    {
      "hrsh7th/nvim-cmp",
      keys = {
         {'<Leader>ff', cmd1, …},
      },
    ...
    {
      "hrsh7th/nvim-cmp",
      keys = {
         {'<Leader>ff', cmd2, …},
      },
    }
  }
)

Where foo.default is a package that defines various plugin specs, including hrsh7th/nvim-cmp with some keys . I would like to overwrite opts, keys, config, etc. of some plugins that are defined by foo.default, e.g. keys of hrsh7th/nvim-cmp. I expected <Leader>ff to be mapped to cmd2 in the example above, i.e. that specs defined later overwrite earlier specs. However, this does not seem to be the case: <Leader>ff is sometimes mapped to cmd1, and sometimes to cmd2. I.e. the merge order is not deterministic.

How is the order in which plugin specs are merged determined? If I define a list of specs {{A}, {B}, {C}} with the same name (e.g. hrsh7th/nvim-cmp), does C overwrite the settings (keys, opts, …) of B or A? Or does the order depend on something else, e.g. dependencies?

Thanks in advance,
Christof

[folke]

specs get parsed in the order they are processed

[cangermueller]

If specs with the same name are ordered {{A}, {B}, {C}}, does this mean that opts/keys/config of C should overwrite B and A? I.e. that the processing order is A -> B -> C?

If this is the case, <Leader>ff should be mapped to cmd2 in the example above, not cmd1. However, this is not what I observe: it is sometimes mapped to cmd1, and sometimes to cmd2.

[cangermueller]

Does the order of specs correspond to the processing order (see my last comment)?