lib/lua-types: init #3213
lib/lua-types: init #3213
Conversation
An initial set of option types for representing values serialisable into lua.
`defaultNullOpts` is generally used for representing lua-options. We should probably a) rename it something like `luaOptions` and switch out the primitive types to use the new `lua-types`.
| anything = types.either lua-types.primitive (lua-types.tableOf lua-types.anything) // { | ||
| description = "lua value"; | ||
| descriptionClass = "noun"; | ||
| }; |
There was a problem hiding this comment.
I'm sure you thought about priorities, but I think adding parentheses would greatly help with readability.
I assume you mean the self-referencing recursive As far as recursive laziness goes, both approaches are exactly the same. No matter how you write it, all self-referencing values do the same thing... I originally wrote it with "local" recursion using lib.fix (self: types.oneOf [
# ...
(tableOf self)
])
// {
description = "lua value";
# ...
}Then I realised that was unnecessary; we don't need |
|
Ok this makes sense. I was wondering if there was any fundamental difference. |
The types in
lua-typesare inspired bypkgs.formats, allowing for a more appropriate option type thantypes.anything.The intention is that we will replace usage of
types.anythingin 90% of cases treewide withlua-types.anything(see #3208). Currently there are ~270 instances ofanythingtreewide.All types in
lua-typessupport inline-lua and raw-lua.lua-types.tableOfwill also serve as a good place to implement merging lists defs and attrs defs into a mixed table, at some point in the future. Ideally we can upstream something similar to nixpkgs too. Again, see #3208 and also NixOS/nixpkgs@master...MattSturgeon:nixpkgs:table.TODO
types.rawLuatolua-typeslua-types.anythinginmkNvimPkugin'ssettingsoptionlua-typesindefaultNullOpts(?)