Question about possible values for opts

[runiq]

The README says this about the plugin spec's possible values for opts:

Property	Type	Description
opts	table or fun(LazyPlugin, opts:table)	opts should be a table (will be merged with parent specs), return a table (replaces parent specs) or should change a table. The table will be passed to the Plugin.config() function. Setting this value will imply Plugin.config()

Passing a table is straightforward. Passing a function fun(LazyPlugin, opts:table) is pretty straightforward too: It means I'll have to do the merging myself. However, I'm not sure what it means to "change a table." Isn't that already included in "return a table"? And if not, what's the difference?

Thanks!

[folke]

You can either make changes to the opts that were passed. This is mostly relevant if you are extending a plugin spec (from LazyVim for example).

Or you can return a completely new table of options, ignoring the opts that were set by the spec you are extending from

[runiq]

Excellent, thanks again :)

[madjxatw]

So am I right that the opts argument actually passed in to fun(LazyPlugin, opts) is the parent spec defined before. In the case of LazyVim, it's the spec defined by LazyVim.

[folke]

It willl always be the parent's merged opts.

[madjxatw]

If I tweak a plugin in two lua files, one using a table to extend the original opts and another using a function to do more stuff, which one will be called first? In other words, in what order are the lua files under the same directory get sourced? alphabetically?

[Chaitanyabsprip]

@madjxatw always write your functions considering they may be called before others.