Hello , discover October's input validation updates! 🎈
View in browser

connected accounting

 
 
Silverfin Developer Community Newsletter
 
 

Hello, Technology Enthusiasts!

 

We’re very excited to welcome you again to our monthly newsletter!

 

😈 Monthly you say? Didn’t we just skip the September newsletter? 

😇 Guilty as charged. But don’t worry, we didn’t go silent. We’ve just been cooking up extra goodies for you to enjoy this time around. 

 

With this in mind, sit back, relax and enjoy a fresh portion of good news from the Silverfin Developer Community.

 

In October’s edition:

  • Input validation: syntax update
  • Input validation: string validation and multiple validations
  • Input validation: min/max exclusive validation
blog-post-divider
 
 

Input validation: syntax update ⚠️

We want to draw your attention to a small update to the syntax for the input_validation tag. In the very first version of our documentation we mentioned that the input_validation tag requires an `as:` attribute to indicate the type of validation taking place. Since the input validation always ties back to an actual input and the type is defined in the input tag, this has been deprecated.

Learn more
 
 

 
 

Input validation: string validation and multiple validations ➕

The attributes `min_length` and `max_length` have been added to the input_validation tag. These attributes allow (as the name suggests) to add validation on input size.

Next to that, we also allow multiple validations. Today, that might not feel groundbreaking, but with more validation types on the horizon (a little bird told me regex validation might be introduced soon as well) this will become super useful.

String length validation
 
 

 
 

Input validation: min/max exclusive validation 0️⃣

Finally, as a last addition to the input validation, we’ve refined the existing min/max validation with two new attributes: `min_exclusive`/`max_exclusive` validation.

Why does this matter? Well, the most common use-case to support these attributes is the scenario where we want to only allow positive or negative numbers in an input field. With the current min/max attributes set to 0, zero itself would also be accepted while zero is not positive nor negative strictly speaking. Hence, excluding zero is what we would need in that situation. Definitely check out our Community case as well on this topic to better understand the use-case!

Silverfin Developer Community
 
 

Thank you for reading!

If you like this newsletter and want to support it please share this email.

 

Write to community@silverfin.com and let us know what you would like to read in the next Silverfin Community Newsletter.

 

Code better. Spam never.

Contact us
Silverfin,  White Collar Factory,  London,  EC1Y 8AF,  United Kingdom,  London

Silverfin, Zuiderpoort - Esplanade, Gaston Crommenlaan 12, 9050 Gent, Belgium

You received this email because you are subscribed to marketing notifications from Silverfin or we’ve received your email address from one of our data providers for the purposes of direct marketing and we are contacting you on the basis of legitimate interest. We believe that you can benefit from the information and complimentary resources shared.

Update your email preferences to choose the types of emails you receive.

Unsubscribe from all future emails.