# CASE: verify your code before saving

**URL:** <https://community.silverfin.com/t/case-verify-your-code-before-saving/1824>\
**Category:** Cases\
**Tags:** guidelines, verify\
**Created:** [June 17, 2020, 3:25pm UTC](https://community.silverfin.com/t/case-verify-your-code-before-saving/1824 "2020-06-17T15:25:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sven](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/sven/32/1495_2.png) [@sven](https://community.silverfin.com/u/sven)\
**Post date:** [June 17, 2020, 3:25pm UTC](https://community.silverfin.com/t/case-verify-your-code-before-saving/1824/1 "2020-06-17T15:25:22Z")

</div>

We’re sure we are not the only one, that when we save our code on firm level, we immediately go to a company file to see the output of our code, and see a syntax error. For example:  
 ![Screenshot 2020-06-17 at 17.16.57](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/f/fd6fb9f07a7d0696d7c95d911e46aba0f1f28a0c.png)

Okay, above can qualify as a rookie mistake but you get the idea: we lose time by saving our code and going back and forth between firm and company level to check when the code is verified.

However 💡

Now there’s a new function in the ribbon! You probably noticed the small bug icon here:  
 ![Screenshot 2020-06-17 at 17.14.28](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/9/95449796620ea2708b95c3e2d001f5640ef8543f.png)

This is actually a **verify** function, in which you can verify your code before saving it.  
If there’s an error, you’ll see where the issue is and why (when hovering over the red cross button):  
 ![Screenshot 2020-06-17 at 17.14.54](https://canada1.discourse-cdn.com/flex030/uploads/getsilverfin/original/2X/2/28ae5ba76f96c56db0660f223335f84298c1e923.png)

Hope this makes up for some time when coding!

PS you can use a shortcut as well: CMD+ENTER (macOS) or ALT+ENTER (WINDOWS)