nix-super/tests/functional/lang/eval-okay-string.nix at 4ff7f5aa9cf15a3c8922ecb2c52875f4f8672899 - max/nix-super - The Forge

max/nix-super

mirror of https://github.com/privatevoid-net/nix-super.git synced 2024-11-22 22:16:16 +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

12 lines

268 B

Nix

Raw Blame History

 "foo" + "bar"
   + toString (/a/b + /c/d)
   + toString (/foo/bar + "/../xyzzy/." + "/foo.txt")
   + ("/../foo" + toString /x/y)
   + "escape: \"quote\" \n \\"
   + "end
 of
 line"
   + "foo${if true then "b${"a" + "r"}" else "xyzzy"}blaat"
   + "foo$bar"
   + "$\"$\""
   + "$"