Conversation
|
I'm supportive of the idea, but the Nix manual states
I guess this is somewhat open to interpretation, but allowing any attribute whatsoever does not seem to be the intent. Could you open a PR to nix that documents the As for this PR, I'd be happy to accept a |
Good idea! Here’s the PR: NixOS/nix#11297 |
This allows specifying metadata info about the flake app. This has been standardized in Nix at NixOS/nix#11297
f9595c4 to
4a41226
Compare
|
@roberth I have made changes based on what was standardised upstream |
roberth
left a comment
There was a problem hiding this comment.
I was thinking ideally meta could be a submodule with freeform type, but that would cause description to error or have a default like "", neither of which is an improvement, so this is probably the best solution for now.
Related:
- optional options could help out with this NixOS/nixpkgs#334680
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
Co-authored-by: Robert Hensing <roberth@users.noreply.github.com>
|
@roberth Does it look good now? |
|
@roberth Is there anything to be done here before merging? This would be useful to implement: juspay/omnix#163 |
| }; | ||
| meta = mkOption { | ||
| type = types.lazyAttrsOf lib.types.raw; | ||
| default = { }; |

This allows specifying metadata info about the flake app. This has been standardised in Nix at NixOS/nix#11297
Here’s an example of its usage: