tomberek

Looks okay. It will need a few additions into the flake.nix to expose it to users.

> What should I add? A few lines similar to these: https://github.com/NixOS/templates/blob/master/flake.nix#L28 (Sorry for the delay.)

Looks good. Requires updates to the root flake.nix to register the new template.

Yeah, there's a pattern in the flake.nix on how to add new ones.

This repo doesn't quite have a process yet and is relatively low volume. At one point I started iterating on things and working on it routinely, but I have not...

Reverting the last commit (4332b9a46711b37bcf73d7de81452efecc55cd75) gives us the following comparison with vanilla Nix: ### Before ```shell $ nix eval .#data --no-eval-cache | nixfmt warning: Git tree '/home/tom/nix/t' is dirty {...

Noticed an **eval failure** when using lib.fileset compared to normal. This is because the value retains a context that it otherwise loses. A more critical location this happens is in...

> I'm not convinced this is a good idea, and it could lead to a lot of anti-patterns. For the record: some [anti-patterns](https://github.com/tomberek/system-arg) that currently work. Warning: ugly hacks. My...

PoC that only allows string values: https://github.com/tomberek/nix/commit/a41ee9e1ce5cc0d374516919e61f11510b112aa6 ``` { description = "A string as an input argument"; inputs.thing.value = "mething233"; outputs = { self, nixpkgs, thing }: with nixpkgs.legacyPackages.x86_64-linux; {...

> @tomberek this looks very promising. Did you have any plans to submit the PoC? I was not planning on it as it was more of a quick hack to...