Support v0.8.4 custom errors
See original GitHub issueSee the announcement article for the new custom error syntax.
For the following code:
/// Too big value for ceiling.
/// @param x Passed input.
error Ud60x18CeilOverflow(uint256 x);
I get this error in VSCode:
Linter: Parse error: missing ‘constant’ at ‘Ud60x18CeilOverflow’ [undefined]
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Solidity v0.8.4 is here - Adds custom structured errors and more!
v0.8.4 adds custom structured errors, bytes.concat(...) , allows more flexible configuration of the SMTChecker and fixes a bug in the Solidity ...
Read more >Support for Solidity v0.8.4 custom errors : r/etherscan - Reddit
v0.8.4 custom errors are a game changer for Solidity - they make it easier to work with errors, more gas efficient, and more...
Read more >Remix supports custom errors in Solidity - Medium
Remix IDE now supports Solidity v0.8.4 including Custom Errors. With Solidity v0.8.4, comes custom errors — where an error message can ...
Read more >EIP-6093: Custom errors for commonly-used tokens
Since the introduction custom errors in Solidity in v0.8.4, ... perhaps the contract name itself could be suggested to help with the ...
Read more >Paul Razvan Berg on Twitter: "Feature request for @etherscan: add ...
add support for Solidity v0.8.4 custom errors. That is, display the name of the custom error that made the tx revert. It's becoming...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, but I knew that in the command-line the linting works. Sorry, I should have made that clear. In the terminal it works since v3.3.5.
I opened an issue in the vscode-solidity repo, the issue must be there. Thanks for your help, Franco!
Ohh, sorry, I totally missed the “VSCode” part in the original issue 😅 Thanks for letting me know!