Paul Berg

I offer a $200 bounty for implementing this feature. DM me on [Telegram](https://t.me/PaulRBerg) once you have the PR.

All good points/ questions, thanks @mds1. > Should all `expect*` cheats have their own overloads that take arrays of addresses? No. The contracts meant to be excluded are (at least...

The lack of this functionality has continued to be a pain. CC @mattsse, @gakonst

As evidenced by this [StackExchange Q&A](https://ethereum.stackexchange.com/q/158768/24693), people keep bumping into hard-to-debug scenarios that could be prevented with a feature that would allow users to exclude certain contracts from being eavesdropped...

@grandizzy I don't think they would. From Matt's code: > If the revert data matches but the address that originated the revert does not, that is considered a failure. I...

> That is because when reverter address is specified vm.expectRevert(address(countRevert)); we're not looking for the next call to revert but rather for the next reverted call to be done by...

`DeployOptimized` is for deployment helpers. The functions you have mentioned serve different purposes (testing).

This is the workaround: ```javascript import pluginDocusaurus from "@docusaurus/eslint-plugin"; export default [ // ... { plugins: { "@docusaurus": pluginDocusaurus, }, rules: pluginDocusaurus.configs.recommended.rules, }, // ... ]; Related thread: https://github.com/facebook/react/issues/28313

I'm on VSCode v1.99.3 and on prettier-vscode v11.0.0, and not even the root `.prettierignore` is respected now :/

HyperEVM should switch to using another chain ID.