Skip to content

Conversation

@steveklabnik
Copy link
Contributor

Fixes #1435

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added/updated tests to cover my changes

@steveklabnik steveklabnik requested a review from a team as a code owner December 9, 2025 21:31
Copy link
Member

@thoughtpolice thoughtpolice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mostly looks good, minor nits

Comment on lines +392 to +396
If you use [direnv](https://direnv.net/) with
[nix-direnv](https://github.com/nix-community/nix-direnv), you can create
a `.envrc` file containing `use flake` to automatically activate the
development environment when entering the directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, if you want, you can replace/reword this bit with:

ln -vsf .envrc.recommended .envrc

Which will just do this for you.

(We should maybe rename it .envrc.nix.recommended or something too, but that's a separate topic.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inside .envrc.recommended, we actually currently have a comment suggesting this command instead, so we should probably make them consistent (I'm not sure which way is better):

echo "source_env .envrc.recommended" >> .envrc

This gives you a shell with:
- A nightly Rust toolchain (including `rustfmt`, `rust-analyzer`, and
`rust-src`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rust-src isn't relevant imo. can probably just replace this whole section with a single sentence:

Once inside the shell, you can run cargo build, cargo test etc. as usual. Other tools like uv, cargo-insta, nextest and more are installed, and so you should be able to follow any other recommendations in this guide as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document Nix setup for devs (what/why/how)

3 participants