feat: add --apply flag
#332
Conversation
|
@mergify rebase |
✅ Branch has been successfully rebased |
|
That crash looks legit. Do you have issues reproducing this locally? |
|
I don't remember that failing |
Allow applying every eval'ed drv to a provided nix expression to evaluate arbitrary fields.
EXAMPLE
```
% ./result/bin/nix-eval-jobs --flake github:NixOS/patchelf#hydraJobs \
--apply \
'drv: {
version = if drv ? version then drv.version else null;
}'
warning: `--gc-roots-dir' not specified
{"attr":"coverage","attrPath":["coverage"],"version":null}
{"attr":"patchelf-win32","attrPath":["patchelf-win32"],"version":"0.18.0"}
{"attr":"patchelf-win64","attrPath":["patchelf-win64"],"version":"0.18.0"}
{"attr":"release","attrPath":["release"],"version":null}
{"attr":"tarball","attrPath":["tarball"],"version":"0.18.0"}
```
|
Sorry for letting this sit so long! I've rebased the PR onto main again and fixed the test. |
| @@ -203,6 +205,26 @@ void worker( | |||
| } | |||
| maybeConstituents = | |||
| Constituents(constituents, namedConstituents); | |||
| } else if (args.applyExpr != "") { | |||
There was a problem hiding this comment.
Do we only run apply if it's not a derivation? Why not always do that?
There was a problem hiding this comment.
@Ma27 do we want to have apply also working if we do have constituents?
There was a problem hiding this comment.
I don't see any reason against it.
There was a problem hiding this comment.
I have no issue with having it aside of constituents, what do you think should the precedence be?
i.e. if --apply produces a constituents attribute, should that be overridden by constituents, or should we side step that question and put the result of apply into a separate attribute?
Allow applying every eval'ed drv to a provided nix expression to evaluate arbitrary fields.
EXAMPLE