In reply to @toonn:matrix.org
Qyriad: What I'm saying is that the `all` in that attrPath is kinda random. If they happened to have called it "everything", the path would be different, and more importantly, what if the default was `{}` would the options types not be accessible at all?

In an attrsOf submodule type, the "definitions" are modules.

The submodule's valueOf.configuration is the submodule's configuration (its options, config, etc).

The attrsOf's valueMeta.attrs is the attrsOf definitions' valueMetas.

The attrsOf type's merge function creates the attrs attr in valueMeta.

So if I have an option foo of type attrsOf, I can define foo.bar = {} and that will result in options.foo.valueMeta.attrs.bar.

Default values are also definitions (just with a low override priority). So in your earlier example all was from the default definition (its value being a module for the services.mastodon.sidekiqProcesses submodule-type to merge).

In an attrsOf submodule type, the "definitions" are attrsets of modules.

The submodule's valueOf.configuration is the submodule's configuration (its options, config, etc).

The attrsOf's valueMeta.attrs is the attrsOf definitions' valueMetas.

The attrsOf type's merge function creates the attrs attr in valueMeta.

So if I have an option foo of type attrsOf, I can define foo.bar = {} and that will result in options.foo.valueMeta.attrs.bar.

Default values are also definitions (just with a low override priority). So in your earlier example all was from the default definition (its value being a module for the services.mastodon.sidekiqProcesses submodule-type to merge).

In an attrsOf submodule type, the "definitions" are attrsets of modules.

The submodule's valueOf.configuration is the submodule's configuration (its options, config, etc).

The attrsOf's valueMeta.attrs is the attrsOf definitions' valueMetas.

The attrsOf type's merge function creates the attrs attr in valueMeta (here).

So if I have an option foo of type attrsOf, I can define foo.bar = {} and that will result in options.foo.valueMeta.attrs.bar.

Default values are also definitions (just with a low override priority). So in your earlier example all was from the default definition (its value being a module for the services.mastodon.sidekiqProcesses submodule-type to merge).

In an attrsOf submodule type, the "definitions" are attrsets of modules.

The submodule's valueOf.configuration is the submodule's configuration (its options, config, etc). See here.

The attrsOf's valueMeta.attrs is the attrsOf definitions' valueMetas.

The attrsOf type's merge function creates the attrs attr in valueMeta (here).

So if I have an option foo of type attrsOf, I can define foo.bar = {} and that will result in options.foo.valueMeta.attrs.bar.

Default values are also definitions (just with a low override priority). So in your earlier example all was from the default definition (its value being a module for the services.mastodon.sidekiqProcesses submodule-type to merge).

In reply to @toonn:matrix.org
Another submodule whose options I can't get at through valueMeta is pixelfed.nginx, `(head (head (services.pixelfed.nginx.type.functor.payload.elemType.functor.payload.modules)).imports).options`

sidekiqProcessOpts =
  mapAttrs
    (name: valueMeta: valueMeta.configuration.options)
    options.services.mastodon.sidekiqProcesses.valueMeta.attrs;