{"id":307,"date":"2022-09-23T14:49:31","date_gmt":"2022-09-23T12:49:31","guid":{"rendered":"https:\/\/ackeeblockchain.com\/blog\/?p=307"},"modified":"2022-09-29T19:22:21","modified_gmt":"2022-09-29T17:22:21","slug":"introducing-tools-for-solidity","status":"publish","type":"post","link":"https:\/\/ackee.xyz\/blog\/introducing-tools-for-solidity\/","title":{"rendered":"Introducing Tools for Solidity \u2013\u2060 VS Code Extension"},"content":{"rendered":"

Have you ever looked for advanced support for Solidity<\/strong> in the editor\/IDE to help you develop smart contracts<\/a>? <\/span><\/p>\n

We have too, and although some extensions for Solidity<\/a> already exist, many of them do not support<\/strong> the latest language features (e.g., user-defined errors, using for directives, \u2026), language server features (e.g., Type hierarchy, Go to type definition) or are simply impractical in terms of how the project is compiled and external dependencies configured.\u00a0<\/span><\/p>\n

Each of them lacked something, and none of them suited our needs, so we created our own. <\/span><\/p>\n

Introducing Tools for Solidity<\/span><\/a>, a Visual Studio Code Solidity extension.<\/span><\/h5>\n

Let’s take a look at the features that are implemented in the first release of the extension: <\/span><\/p>\n

Go to definition<\/strong><\/p>\n

\"\"<\/p>\n

Go to type definition<\/strong><\/p>\n

\"\"<\/p>\n

Go to implementation<\/strong><\/p>\n

Find implementations of an unimplemented function or modifier.<\/p>\n

\"\"<\/p>\n

Find references<\/strong><\/p>\n

\"\"<\/p>\n

Type hierarchy<\/strong><\/p>\n

\"\"<\/p>\n

Also works for virtual functions.<\/p>\n

\"\"<\/p>\n

Document links for import directives<\/strong><\/p>\n

\"\"<\/p>\n

Hover<\/strong><\/p>\n

Includes links to documentation for OpenZeppelin contracts.<\/p>\n

\"\"<\/p>\n

Code lens with number of references<\/strong><\/p>\n

Number of references is shown above each declaration.<\/p>\n

\"\"<\/p>\n

Document symbols<\/strong><\/p>\n

\"\"<\/p>\n

Diagnostics with compiler errors and warnings<\/strong><\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Rename<\/strong><\/p>\n

\"\"<\/p>\n

Solidity projects opened in VS Code with our extension are automatically compiled<\/strong>, and all necessary compiler versions are automatically downloaded. If a project contains compilation errors, our tool will perform a partial analysis of the part of the project that does not depend on the part containing the error.<\/span><\/p>\n

Compiling a project with external dependencies can often work without configuration. NPM packages (if installed) are detected automatically. Nevertheless, our extension provides various configuration options<\/strong>.<\/span><\/p>\n

Tools for Solidity<\/span> <\/strong>with the Woke<\/a>, our development and testing framework for Solidity, LSP server in the background utilizes incremental compilation<\/strong>, which means that only modified files (and their dependencies) are recompiled on the change to the source files.\u00a0<\/span><\/p>\n

This results in an almost immediate response<\/strong> of the extension while editing a code. The fast recompilation time also allows us to inform the user of a security flaw while writing code. Results from Woke vulnerability detectors<\/strong> are shown together with compiler warnings and errors.<\/span><\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

We are excited to make our VS Code Solidity extension publicly available on the marketplace.\u00a0<\/strong><\/p>\n

\"\"<\/a><\/h4>\n

What’s next?<\/h4>\n

In the further development of our extension, we would like to focus on presenting and giving the user the possibility to interact with other Woke functionalities. For example, it could visualize the code coverage of our fuzzer<\/strong> or have a button to generate a test template<\/strong> for our future Solidity testing framework. All of this should be possible just through the extension, without using the command line.<\/p>\n","protected":false},"excerpt":{"rendered":"

Have you ever looked for advanced support for Solidity in the editor\/IDE to help you develop smart contracts?<\/p>\n","protected":false},"author":11,"featured_media":341,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[65,10],"tags":[67,64,68,74,75,69],"class_list":["post-307","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcements","category-ethereum","tag-announcement","tag-security","tag-solidity","tag-tools-for-solidity","tag-vs-code","tag-woke"],"aioseo_notices":[],"featured_image_src":"https:\/\/ackee.xyz\/blog\/wp-content\/uploads\/2022\/09\/ABCH-Solidity-Cover-600x400.png","featured_image_src_square":"https:\/\/ackee.xyz\/blog\/wp-content\/uploads\/2022\/09\/ABCH-Solidity-Cover-600x600.png","author_info":{"display_name":"Andrea Nov\u00e1kov\u00e1","author_link":"https:\/\/ackee.xyz\/blog\/author\/andrea-novakova\/"},"_links":{"self":[{"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/posts\/307","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/comments?post=307"}],"version-history":[{"count":0,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/posts\/307\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/media\/341"}],"wp:attachment":[{"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/media?parent=307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/categories?post=307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ackee.xyz\/blog\/wp-json\/wp\/v2\/tags?post=307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}