-
Notifications
You must be signed in to change notification settings - Fork 169
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
allow gas-custom-errors
rule to properly handle custom errors inside require statements
#602
Comments
Any updates on this? It would be useful to have, as custom |
I will address several issues in the upcoming weeks and get a new release before new year |
refer to this pr If you find any other case , please advice |
Thanks! Is there a release I can reference with this fix? |
not yet
but soon enough
will be before 2025
…On Fri, Dec 20, 2024 at 5:56 PM Shawn ***@***.***> wrote:
Thanks! Is there a release I can reference with this fix?
—
Reply to this email directly, view it on GitHub
<#602 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVOBPIECIDKXRFQL6X5DSNL2GSAA7AVCNFSM6AAAAABOEILR7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXG4YDKNZYGI>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
--
Diego Bale
Tech Lead - Senior Solidity Dev | protofire.io
<http://t.me/eldanba>: @eldanba
✉️: ***@***.***
[image: linkedin icon] <https://www.linkedin.com/in/diegobale/>
The content of this email is confidential and intended for the recipient
specified in the message only. It is strictly forbidden to share any part
of this message with any third party, without the written consent of the
sender. If you received this message by mistake, please reply and follow
with its deletion, so we can ensure such a mistake does not occur.
|
Solidity 0.8.26 introduces the ability to use custom errors within require statements. When using this functionality (custom error in conjunction w/ require statement), solhint faultily marks the line as having a
gas-custom-errors
infractionThe text was updated successfully, but these errors were encountered: