Open
Conversation
It recurses into attrSets, showing all the terms of the `lib` output. Here's an example `nix flake show`: ``` ⋮ ├───lib │ ├───configuration: lambda │ ├───defaultConfiguration: lambda │ └───just │ └───some │ └───nested │ └───values │ ├───aList: list │ ├───aPath: path │ ├───aString: string │ ├───anInt: int │ └───itsNull: null ⋮ ```
Collaborator
|
Unfortunately this goes into an infinite recursion on the (Of course Nixpkgs could provide its own |
Contributor
Author
|
What do you think is the right way to solve this? Should we support this recursion, or patch Nixpkgs to not be self-referential? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It recurses into attrSets, showing all the terms of the
liboutput.Here's an example
nix flake show: