-5
lib/fileset/README.md
-5
lib/fileset/README.md
···- (+) That can change depending on which files are included, so if it's used for `fileFilter`- (+) If necessary, this restriction can be relaxed later, the opposite wouldn't be possible-- If/Once a function exists that can optionally include a path depending on whether it exists, the error message for the path not existing in `_coerce` should mention the new function
+31
lib/fileset/default.nix
+31
lib/fileset/default.nix
···- [`lib.fileset.trace`](#function-library-lib.fileset.trace)/[`lib.fileset.traceVal`](#function-library-lib.fileset.trace):······+lib.fileset.maybeMissing: Argument ("${toString path}") is a string-like value, but it should be a path instead.''+lib.fileset.maybeMissing: Argument is of type ${typeOf path}, but it should be a path instead.''
+2
-1
lib/fileset/internal.nix
+2
-1
lib/fileset/internal.nix
···
+36
-1
lib/fileset/tests.sh
+36
-1
lib/fileset/tests.sh
···-expectFailure 'toSource { root = ./.; fileset = ./a; }' 'lib.fileset.toSource: `fileset` \('"$work"'/a\) is a path that does not exist.'+expectFailure 'toSource { root = ./.; fileset = ./a; }' 'lib.fileset.toSource: `fileset` \('"$work"'/a\) is a path that does not exist.expectFailure 'union ./. ./.' 'lib.fileset: Directly evaluating a file set is not supported.···+expectFailure 'maybeMissing "someString"' 'lib.fileset.maybeMissing: Argument \("someString"\) is a string-like value, but it should be a path instead.'+expectFailure 'maybeMissing null' 'lib.fileset.maybeMissing: Argument is of type null, but it should be a path instead.'# TODO: Once we have combinators and a property testing library, derive property tests from https://en.wikipedia.org/wiki/Algebra_of_sets