-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Stuctured command stability #7611
Stuctured command stability #7611
Conversation
The diff is quite large and it's not clear at a glance what the change actually is about. Can you elaborate in the PR description what exactly changed in terms of user-visible behavior? This seems more fitting:
PS: "Clean up" should be a forbidden phrase in commit messages. |
🎉 All dependencies have been resolved ! |
The diff is large because of the other PRs this depends on. |
Draft because https://github.com/apps/dpulls is not cutting it, and the chained diffs are confusing. |
b16d91f
to
913888f
Compare
Discussed in the Nix team meeting 2023-04-03:
|
913888f
to
e97c91f
Compare
This is now just the infrastructure, as discussed. |
e97c91f
to
1a71eca
Compare
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.
Just the nit, otherwise lgtm!
1a71eca
to
3c059ce
Compare
Prior to this, there was an ad-hoc whitelist in `main.cc`. Now, every command states its stability. In a future PR, we will adjust the manual to take advantage of this new information in the JSON. (It will be easier to do that once we have some experimental feature docs to link too; see NixOS#5930 and NixOS#7798.)
3c059ce
to
4a0b893
Compare
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-04-03-nix-team-meeting-minutes-46/27008/1 |
Prior to this, there was an ad-hoc whitelist in
main.cc
. Now, every command states its stability.In a future PR, we will adjust the manual to take advantage of this new
information in the JSON. It will be easier to do that once we have some experimental feature docs to link too; see #5930 and #7798.)