I marked this as stale due to inactivity. → More info

I'm still using this patch to make my config work.

Looking good, but can you extend the test cases in pkgs/pkgs-lib/tests/formats.nix with this?

Ok, done.

Nice, thanks!

I believe this caused a weird conflict in my config:

I have a configuration which uses pkgs.types.yaml, and ends up merging two files like this:

{
   services.foo.config.bar = [ "/var/lib/foo" "/var/lib/bar" ];
  # another file..
   services.foo.config.bar = [ "/var/lib/baz" "/var/lib/quux" ];
}

This breaks due to types.path believing anything that is coercible to a string and starts with a / when coerced is a path. This includes: paths, strings, null, int, float, bool, lists of the previous, or having an outPath or a __toString. This works when there's only one definition (as merge doesn't actually cast the object to a path), but even so, it is quite obvious that a path type is not the right type for the entire option, as it breaks the behavior of lists being mergable.

An easy solution to this is to reorder the entries, to prefer (listOf ...) over path, but that seems a bit fragile.