See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
#!/usr/bin/env node | |
const fizz = "Fizz"; | |
const buzz = "Buzz"; | |
const fizzbuzz = `${fizz}${buzz}`; | |
const Rx = require('rxjs/Rx'); | |
Rx.Observable.range(1,100) | |
.map(n => n % 15 === 0 ? fizzbuzz : (n % 3 === 0 ? fizz : (n % 5 === 0 ? buzz : n))) |
Most of our tasks as software engineers are related to forms. Sign up forms, sing in forms, onboarding forms, etc. So today we are going to practice how to validate any form data using accumulative errors so we can now in just one method invocation what are the errors our form contains.
Our task for today's practice is to write a program to be able to validate if the data contained in a form with the following information is valid or not.
use yew::events::ChangeData; | |
use yew::web_sys::File; | |
use yew::prelude::*; | |
pub struct MyFileInput { | |
link: ComponentLink<Self>, | |
file: Option<File>, | |
} | |
pub enum Msg { |