Update devcontainer.json

[Dargon789]

Dargon789/foundry@48533bb

Summary by Sourcery

Chores:

• Tidy up or adjust the .devcontainer/devcontainer.json configuration used for local development.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The pull request updates the development container configuration in .devcontainer/devcontainer.json; reviewers should focus on how the container image, extensions, settings, and workspace mounting behavior have changed and ensure they still match the project’s development needs.

File-Level Changes

Change	Details	Files
Updated the devcontainer configuration for the project’s development environment.	Adjusted the base image or features used for the development container to better match project dependencies or tooling. Updated VS Code-specific configuration such as extensions, settings, or forwardPorts to streamline local development. Modified workspace mounting or postCreate/postStart commands to improve setup reliability or performance.	.devcontainer/devcontainer.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the development container configuration, moving from a Hardhat and Node.js-centric environment to one tailored for Rust and Foundry development. The changes involve adopting a custom Dockerfile, integrating Rust-specific VS Code extensions and settings, enhancing the shell experience with Zsh, and optimizing Rust build times through cargo cache mounts. This update aims to provide a more robust and efficient development setup for projects utilizing the Foundry framework.

Highlights

• Development Environment Shift: The dev container configuration has been updated to transition from a Hardhat/Node.js setup to a dedicated Rust/Foundry development environment, utilizing a custom Dockerfile.
• VS Code Extension and Settings Update: The set of VS Code extensions has been revised, removing Node.js/Solidity tools and adding a comprehensive suite for Rust (rust-analyzer, crates, TOML), Python, ESLint, and Bun, along with specific Rust Analyzer settings.
• Enhanced Shell Experience and Rust Toolchain Management: The common-utils feature has been integrated to provide Zsh, Oh My Zsh, and package upgrades, while the postCreateCommand now focuses on rustup for managing the Rust toolchain.
• Cargo Cache Optimization: New bind mounts have been added for .cargo/registry and .cargo/git to leverage local caching, aiming to improve Rust build performance within the dev container.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request overhauls the devcontainer configuration, transitioning from a Hardhat/Node.js environment to a Foundry/Rust setup. The new configuration is well-structured, leveraging a custom Dockerfile and caching Cargo dependencies for better performance. I've added a couple of suggestions to improve the maintainability and robustness of the devcontainer.json file. Specifically, I've pointed out a potential issue with enabling all Cargo features for rust-analyzer and suggested a way to make the volume mount paths more dynamic.