Skip to content
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

RFC 166 implementation tracking issue #153

Open
10 of 15 tasks
infinisil opened this issue Mar 12, 2024 · 14 comments
Open
10 of 15 tasks

RFC 166 implementation tracking issue #153

infinisil opened this issue Mar 12, 2024 · 14 comments

Comments

@infinisil
Copy link
Member

infinisil commented Mar 12, 2024

Now that RFC 166 is accepted, let's commence with the implementation!

Here's a very rough todo-list, most of which will be fairly quick.

Ping @piegamesde @tomberek @0x4A6F @Sereja313 @dasJ

@tomberek
Copy link
Contributor

Proposal: do reformatting in the NixOS org with a few non-nixpkgs repos first

@infinisil infinisil pinned this issue Mar 13, 2024
@Atemu
Copy link
Member

Atemu commented Mar 13, 2024

Proposal: After what @tomberek suggested is done and successful, do formatting of Nixpkgs in a subset of Nixpkgs first (i.e. pkgs/by-name/)

@Kreyren
Copy link

Kreyren commented Mar 17, 2024

https://github.com/Kreyren/nixos-config/blob/dc0dbb6f15c4d8656b26220645793a06d10fa3ea/nixos/users/kreyren/home/modules/prompts/starship/starship.nix#L3-L14 (best seen in raw)

RFC @infinisil Is this known issue that is actionable by RFC166? I read through it don't see it anywhere (if tabs are used it causes the prompt to be rendered with long indentation instead of the indentation being removed from the declaration, affects most of nix modules)

@piegamesde
Copy link
Member

This looks unlikely to be a desired output according to the RFC format. Now that the PR is merged, please simply open an issue for it.

infinisil added a commit to NixOS/nixos-homepage that referenced this issue Mar 19, 2024
As [established by RFC
166](https://github.com/NixOS/rfcs/blob/master/rfcs/0166-nix-formatting.md#nix-formatter-team),
see also NixOS/nixfmt#153.

Before merging I'd like all members to give their okay with their entry.
Ping @NixOS/nix-formatting

---------

Co-authored-by: Sereja313 <[email protected]>
@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/formatting-team-meeting-2024-03-19/41845/1

@Kreyren
Copy link

Kreyren commented Mar 20, 2024

This looks unlikely to be a desired output according to the RFC format. Now that the PR is merged, please simply open an issue for it. -- @piegamesde (#153 (comment))

Referencing comment by @roberth in NixOS/nix#8874 (comment)

Got referred to RFC166 from RFC137 about this issue in relation to addressing NixOS/nix#8874

@piegamesde
Copy link
Member

@Kreyren please just open a new issue with input, current output and desired output and I'll look at it. Simply linking to weird looking code does not give me enough context to understand the situation.

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/tweag-nix-dev-update-56/43035/1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/nixf-tidy-static-semantic-linter-for-nix-help-me-to-integrate-it-with-github-actions-pr-reviews/43911/2

webframp added a commit to webframp/dotfiles that referenced this issue Apr 23, 2024
Currently using alejandra for now, this isn't needed

fixes the following warning:

trace: warning: nixfmt was renamed to nixfmt-classic. The nixfmt attribute may be used for the new RFC 166-style formatter in the future, which is currently available as nixfmt-rfc-style

More details in:

NixOS/nixfmt#153
@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506/3

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506/8

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/satisfaction-survey-from-the-new-rfc-166-formatting/49758/1

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/why-does-the-nixos-infrastructure-have-to-be-hosted-in-a-centralized-way/46789/36

@gabyx
Copy link

gabyx commented Aug 26, 2024

@infinisil et. al.: ❤️ Thanks a lot for pushing this and the hard work on it! I am happy if that debate is soon over =) and we have some opiniated way to not disgress again and again into whitespace debates in PRs. Having a 90% solution is so much better then having nothing which puts Nixpkgs back to middleages.

antoineco added a commit to antoineco/dotfiles that referenced this issue Sep 5, 2024
nixpkgs-fmt was archived[1] in favour of nixfmt[2], which implements the
Nix RFC 166[3].

See NixOS/nixfmt#153 for further details about the progress of the
implementation.

[1]: https://x.com/zimbatm/status/1816148339131343058
[2]: https://github.com/NixOS/nixfmt?tab=readme-ov-file#readme
[3]: https://github.com/nix-rfc-101/rfcs/blob/aaf1613f/rfcs/0166-nix-formatting.md
antoineco added a commit to antoineco/antoineco.github.io that referenced this issue Sep 6, 2024
nixpkgs-fmt was archived[1] in favour of nixfmt[2], which implements the
Nix RFC 166[3].

See NixOS/nixfmt#153 for further details about the progress of the
implementation.

[1]: https://x.com/zimbatm/status/1816148339131343058
[2]: https://github.com/NixOS/nixfmt?tab=readme-ov-file#readme
[3]: https://github.com/nix-rfc-101/rfcs/blob/aaf1613f/rfcs/0166-nix-formatting.md
antoineco added a commit to antoineco/antoineco.github.io that referenced this issue Sep 6, 2024
nixpkgs-fmt was archived[1] in favour of nixfmt[2], which implements the
Nix RFC 166[3].

See NixOS/nixfmt#153 for further details about the progress of the
implementation.

[1]: https://x.com/zimbatm/status/1816148339131343058
[2]: https://github.com/NixOS/nixfmt?tab=readme-ov-file#readme
[3]: https://github.com/nix-rfc-101/rfcs/blob/aaf1613f/rfcs/0166-nix-formatting.md
antoineco added a commit to antoineco/antoineco.github.io that referenced this issue Sep 6, 2024
nixpkgs-fmt was archived[1] in favour of nixfmt[2], which implements the
Nix RFC 166[3].

See NixOS/nixfmt#153 for further details about the progress of the
implementation.

[1]: https://x.com/zimbatm/status/1816148339131343058
[2]: https://github.com/NixOS/nixfmt?tab=readme-ov-file#readme
[3]: https://github.com/nix-rfc-101/rfcs/blob/aaf1613f/rfcs/0166-nix-formatting.md
antoineco added a commit to antoineco/antoineco.github.io that referenced this issue Sep 6, 2024
nixpkgs-fmt was archived[1] in favour of nixfmt[2], which implements the
Nix RFC 166[3].

See NixOS/nixfmt#153 for further details about the progress of the
implementation.

[1]: https://x.com/zimbatm/status/1816148339131343058
[2]: https://github.com/NixOS/nixfmt?tab=readme-ov-file#readme
[3]: https://github.com/nix-rfc-101/rfcs/blob/aaf1613f/rfcs/0166-nix-formatting.md
kai-tub added a commit to kai-tub/quadlet-nix that referenced this issue Sep 23, 2024
Apply [official RFC nixfmt](NixOS/nixfmt#153).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

7 participants