fix(lib.types.stringable): ensures store paths are realized#286
Merged
fix(lib.types.stringable): ensures store paths are realized#286
Conversation
sometimes passing a regular nix store path like `./somepath` will not
get realized unless you call `builtins.path { path = ./somedir; }`
When a user uses a type like this, and provides a store path to it, they
expect it to be provisioned. It is also safe to call multiple times on a
value. So we should handle this in this type.
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
1 participant
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.
sometimes passing a regular nix store path like
./somepathwill not get realized unless you callbuiltins.path { path = ./somedir; }When a user uses a type like this, and provides a store path to it, they expect it to be provisioned. It is also safe to call multiple times on a value. So we should handle this in this type.