This compromises the ability to `inputs'?formatter`, but that seems like a particularly rare use case. Instead, we treat `inputs'` as another "programmatic" as opposed to "polished" interfaces, similar to the `config` vs flake attributes distinction. The programmatic interfaces always prioritize laziness whereas the polished interfaces may choose to omit known-missing things, to a reasonable degree. |
||
|---|---|---|
| .. | ||
| perSystem-memoize | ||
| nix-unit.nix | ||
| perSystem-memoize.nix | ||
| README.md | ||
| template.nix | ||
Running the tests
These tests can be run locally with the hci effect run command. This gives
the tests access to a proper nix daemon and the network.
Designed for convenient deployments, it needs some information from git. You
may use --no-token to disable this functionality if you're getting errors, or
if you're asked to log in.
Example:
hci effect run --no-token default.effects.tests.template