nix-super/tests/functional/lang/eval-okay-tojson.nix at 8f3253c6f4041f500631e1dac5ba75f335e9c70a - max/nix-super - The Forge

max/nix-super

mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-30 01:26:15 +02:00

John Ericson 68c81c7375 Put functional tests in tests/functional

I think it is bad for these reasons when `tests/` contains a mix of
functional and integration tests

 - Concepts is harder to understand, the documentation makes a good
   unit vs functional vs integration distinction, but when the
   integration tests are just two subdirs within `tests/` this is not
   clear.

 - Source filtering in the `flake.nix` is more complex. We need to
   filter out some of the dirs from `tests/`, rather than simply pick
   the dirs we want and take all of them. This is a good sign the
   structure of what we are trying to do is not matching the structure
   of the files.

With this change we have a clean:
```shell-session
$ git show 'HEAD:tests'
tree HEAD:tests

functional/
installer/
nixos/
```

2023-10-06 09:05:56 -04:00

13 lines

260 B

Nix

Raw Blame History

 builtins.toJSON
   { a = 123;
     b = -456;
     c = "foo";
     d = "foo\n\"bar\"";
     e = true;
     f = false;
     g = [ 1 2 3 ];
     h = [ "a" [ "b" { "foo\nbar" = {}; } ] ];
     i = 1 + 2;
     j = 1.44;
     k = { __toString = self: self.a; a = "foo"; };
   }