-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
nixfmt-classic: add (eventual) deprecation and removal #447790
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
I wonder if we should be doing the deprecation (i.e. step 2) at the underlying
haskellPackages.nixfmtpackage? Since the top-levelnixfmt-classicis already just an alias for it...I can't see if/how/where the
haskellPackagesset handles aliases and deprecation, though... Nothing obvious in the entrypoint. Maybe @NixOS/haskell will know?Whatever we do should be gated behind
config.allowAliases, of course.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.
Needs to be implemented manually, you can grep for
allowAliases. Note that package removal is currently not possible (in a sensible way), but will probably be implemented sometime this autumn (cc @wolfgangwalther).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.
I spoke to @wolfgangwalther async:
So I believe the correct thing to do is merge this as-is, then move the deprecation into the
haskellPackagesscope if/when that package-set adds support for deprecating specific packages.Naïvely, we could add an overlay to the end of haskellPackages's extensions stack, and have that overlay implement the deprecations:
However, this means that the package will still be present without any deprecation when
allowAliases = false, which is unusual. That's because the package is automatically generated from hackage, so we can't move its base definition to a conditional extension.