-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible way to expose devshell.toml's path? #95
Comments
Do you want the file to be added to the /nix/store or just point to its location in the repo? Where is that path being used? |
A couple of days ago, I also had a thought on relative-to-toml file paths in the context of wanting to load per-repo devshell modules (without resorting to |
The module has a _file attribute that exposes its location. Ideally, it would be possible to set the type of attribute to Otherwise, we will have to revert to something less ideal like a post-processing step. Or install |
E.g. useful for toml strings that should represent a relative file to the toml file. fixes: numtide#95
Issue
I wanted to add a feature to the git.hooks module to allow specifying a path to a hook. I got all the logic wired in and working, but the issue is that I have to specify a full path 😞
nix doesn't seem to have the ability to convert a string with a relative path to a full path, and since toml doesn't have a native notion of a path, I'm kinda stuck.
builtins.toPath
is depricated and doesn't really do anything.The only work around I can think of is if we define a variable somewhere containing the current devshell.toml's path. Then I can specify a path relative to the location of the devshell.toml to the git.hook source file. I'm sure this will come in handy for similar reasons in other modules.
I guess the alternative would be to leave it as a nix only option, but setting from toml would be ideal.
Context
my devshell.toml is not at the root of the project, otherwise I probably would have thought to use DEVSHELL_ROOT
The text was updated successfully, but these errors were encountered: