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
vscode-extensions.b4dm4n.nixpkgs-fmt init at 0.0.1 #95227
vscode-extensions.b4dm4n.nixpkgs-fmt init at 0.0.1 #95227
Conversation
48fe6a1
to
81e5d82
Compare
do you mind rebasing on latest master instead of merging? |
''; | ||
|
||
meta = with stdenv.lib; { | ||
description = "Format nix files with nixpkgs-fmt"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add homepage
I'm currently trying to rebase, but it goes through +10k commits with tons of merge issues, so i've decided to try |
The `--no-build-output` flag that is added by default is only valid for the old cli, which is not used when flakes are used. Follow-up to c9daa81.
Since version 3.1.0, it has been moved to `params/parameters.toml`. Note that an alternative to appending would be to use `params/private-parameters.toml` but in our case, I don't think it matters much as we don't keep the build directory.
Motivation for this change
add vscode extensions
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)