Revert ".devcontainer: nixfmt-rfc-style -> nixfmt"#431258
Revert ".devcontainer: nixfmt-rfc-style -> nixfmt"#431258wolfgangwalther merged 2 commits intoNixOS:masterfrom
Conversation
jfly
left a comment
There was a problem hiding this comment.
I know nothing about how devcontainers are used here, but this seems fine to me.
The alias should be dropped only once `pkgs.nixfmt` is unlikely to be nixfmt-classic. I.e. after nixfmt 1.0 is in a stable release, but before the nixfmt-rfc-style alias starts warning. See NixOS#425583
wolfgangwalther
left a comment
There was a problem hiding this comment.
I know nothing about .devcontainer either, but nixfmt-rfc-style seems like the safe choice as long as it still exists.
|
It seems like this can be changed whenever the |
If so, should I amend the |
|
I'm not 100% sure about my statement. I looked at the source code for that container a bit, and I'm not sure from which nixpkgs revision it pulls packages. Might as well just be the current latest unstable - no idea. |
|
We will only find out if somebody actually uses this thing. With Thus, I'm merging this to be on the safe side. |
Reverts #430330
As per #425583 and #430330 (comment), I believe this was bumped prematurely.
Unless the devcontainer is using the in-tree copy of nixpkgs, the CI-pinned revision, or some other known-to-be up-to-date revision... If we can guarantee the devcontainer always uses an up-to-date nixpkgs, then this can be closed.
If the devcontainer is using nixpkgs from (e.g.) the NIX_PATH, then we don't know whether
pkgs.nixfmtis the rfc-style formatter or the classic version. That's because NIX_PATH may contain an old revision or a stable release.