<p>We are going to create a single component that supports text, textarea, select, radio, and checkbox. It will absorb all implementation differences for different inputs and will allow us using a unified component in our Formik forms.</p>
<p>When I start on a new project, I always try to abstract specific libraries away by defining my own components. This brings some benefits</p>
<ul>
<li>Simplify the code by moving the complex/common part into my custom component.</li>
<li>Have the ease of changing the underlying dependency without going through a crazy refactoring, but rather only updating my custom component</li>
</ul>
<p>This time we are going to create a component that seamlessly works with any input type. Then we’re going to integrate it with react-bootstrap without touching any of our forms, but just updating our custom input component.</p>
<p>Let’s see what we’re building first before going into implementation details. This is how our form will look like</p>
<p><img src="https://s3.us-east-1.amazonaws.com/resource.mixa.site/meric/posts/img/creating-a-unified-formik-input-field-to-support-all-input-types-seamlessly/form.png" priority="1"></p>
<p>And here is how we are going to define our form. It’s simple, clean, easy-to-read, right?</p>
<pre><code>&#x3C;form onSubmit={props.handleSubmit}>
  &#x3C;FormItem
    type="text"
    label="Full Name"
    name="fullName"
  />
  &#x3C;FormItem
    type="textarea"
    label="Comment"
    name="comment"
  />
  &#x3C;FormItem
    type="select"
    label="Default Currency"
    name="defaultCurrency"
    options={[
      {value: 'USD', label: 'American Dollar'},
      {value: 'EUR', label: 'Euro'}
    ]}
  />
  &#x3C;FormItem
    type="radio"
    label="Gender"
    name="gender"
    options={[
      {value: 'male', label:'Male'},
      {value: 'female', label:'Female'},
      {value: 'other', label:'Other'}
    ]}
  />
  &#x3C;FormItem
    type="checkbox"
    label="Hobbies"
    name="hobbies"
    options={[
      {value: 'baking', label:'Baking'},
      {value: 'dance', label:'Dance'}
    ]}
  />
  &#x3C;button type="submit">Submit&#x3C;/button>
&#x3C;/form>
</code></pre>
<p>Ok, now let’s start implementing it.</p>
<h2 id="component-structure"><a aria-hidden="true" tabindex="-1" href="#component-structure"><span class="icon icon-link"></span></a>Component structure</h2>
<p>To make it easier to understand, you can see the structure of the components below. In the following sections, we are going to implement FormItem, FormInput, TextInput, TextAreaInput, SelectInput, and CheckInput.</p>
<p><img src="https://s3.us-east-1.amazonaws.com/resource.mixa.site/meric/posts/img/creating-a-unified-formik-input-field-to-support-all-input-types-seamlessly/components.png"></p>
<h2 id="creating-the-container-component"><a aria-hidden="true" tabindex="-1" href="#creating-the-container-component"><span class="icon icon-link"></span></a>Creating the container component</h2>
<pre><code>import {connect} from 'formik';

const FormItem = connect(props => {
  const { label, ...inputProps } = props;
  const { errors, touched } = props.formik;
  return (
    &#x3C;div>
      {label &#x26;&#x26; &#x3C;label>{label}&#x3C;/label>}

      &#x3C;FormInput {...inputProps} />

      {errors[inputProps.name] &#x26;&#x26; touched[inputProps.name] &#x26;&#x26; &#x3C;p>{errors[inputProps.name]}&#x3C;/p>}
    &#x3C;/div>
  );
});
</code></pre>
<p>This will contain whatever a form field requires: a label, an input field, and validation errors. Line 8 renders the label if user provided the label prop. Line 10 renders the input component and line 12 renders the validation errors if there is any.</p>
<p>You might be asking where <code>props.formik</code> came from. It is added in the props by <a href="https://jaredpalmer.com/formik/docs/api/connect">connect</a> method we use in line 3. Now our component will have the full formik context.</p>
<p>You can also use Formik’s <a href="https://jaredpalmer.com/formik/docs/api/field">Field component</a> which is aware of the Formik context without you doing anything. You just need to adjust this FormItem component to make it work with Field component.</p>
<h2 id="deciding-which-input-to-render"><a aria-hidden="true" tabindex="-1" href="#deciding-which-input-to-render"><span class="icon icon-link"></span></a>Deciding which input to render</h2>
<pre><code>const FormInput = props => {
    switch (props.type) {
        case 'radio':
        case 'checkbox':
            return CheckInput(props);
        case 'select':
            return SelectInput(props);
        case 'textarea':
            return TextAreaInput(props);
        default:
            return TextInput(props);
    }
}
</code></pre>
<p>This one is straight-forward. It just renders the correct input component based on the type prop and passes all props down to that component. We are going to handle radio and checkbox in the same component, namely CheckInput, since they’re quite similar.</p>
<h2 id="implementing-input-components"><a aria-hidden="true" tabindex="-1" href="#implementing-input-components"><span class="icon icon-link"></span></a>Implementing input components</h2>
<p>Every prop you pass to the FormItem will eventually be passed into the actual input element except the ones we defined for our specific use</p>
<ul>
<li>
<p><code>label</code> is used in FormItem to render the label, so it’s not actually a prop for the input field</p>
</li>
<li>
<p><code>options</code> is used to pass the list of options in select, radio and checkbox elements. It will be an array of options like</p>
</li>
</ul>
<pre><code>[
  {value: 'val1', label: 'Option 1'},
  {value: 'val2', label: 'Option 2'}
]
</code></pre>
<p>In addition to the props passed by the user, we should also pass additional props to make it work with Formik such as <code>value</code>, <code>onClick</code>, <code>onBlur</code> etc. We’re going to handle the extraction of the input props in <code>extractInputProps</code> method. Let’s leave it’s implementation to the next section.</p>
<h3 id="textinput-and-textareainput"><a aria-hidden="true" tabindex="-1" href="#textinput-and-textareainput"><span class="icon icon-link"></span></a>TextInput and TextAreaInput</h3>
<p>Here how we define our text and textarea inputs. Nothing fancy, just pass the props and render the input element.</p>
<pre><code>const TextInput = props => &#x3C;input {...extractInputProps(props)} />

const TextAreaInput = props => &#x3C;textarea {...extractInputProps(props)} />
</code></pre>
<h3 id="selectinput"><a aria-hidden="true" tabindex="-1" href="#selectinput"><span class="icon icon-link"></span></a>SelectInput</h3>
<p>Next, let’s define our select input. It’s similar to the previous ones, but we also need to render a list of options which were passed in the <code>options</code> prop in FormItem.</p>
<pre><code>const SelectInput = props => (
  &#x3C;select {...extractInputProps(props)}>
    &#x3C;option value="">Select a value&#x3C;/option>
    {props.options.map(o =>
      &#x3C;option key={o.value} value={o.value}>{o.label || o.value}&#x3C;/option>)}
  &#x3C;/select>
);
</code></pre>
<h3 id="checkinput-for-radio-and-checkbox"><a aria-hidden="true" tabindex="-1" href="#checkinput-for-radio-and-checkbox"><span class="icon icon-link"></span></a>CheckInput for radio and checkbox</h3>
<p>Now combining above two, it’s not too hard to understand radio and checkbox. Radio/Checkbox behaves different than other input elements, which we will handle in <code>extractInputProps</code> method.</p>
<pre><code>const CheckInput = props => (
  &#x3C;Fragment>
    {props.options.map(option => (
      &#x3C;label key={option.value}>
        &#x3C;input {...extractInputProps(props, option)} />
        {option.label || option.value}
      &#x3C;/label>
    ))}
  &#x3C;/Fragment>
);
</code></pre>
<h2 id="defining-extractinputprops-method"><a aria-hidden="true" tabindex="-1" href="#defining-extractinputprops-method"><span class="icon icon-link"></span></a>Defining extractInputProps method</h2>
<p>This method will accept <code>props</code> and <code>option</code> as parameters. <code>option</code> will be passed only by select/radio/checkbox while rendering each option coming from <code>options</code> prop.</p>
<pre><code>function extractInputProps({formik, options,...otherProps}, option) {
  const props = {
    value: formik.values[otherProps.name],
    onChange: formik.handleChange,
    onBlur: formik.handleBlur,
    ...otherProps
  }

  if (props.type === 'radio') {
    // set additinoal props for radio
  } else if (props.type === 'checkbox') {
    // set additinoal props for checkbox
  }

  return props;
}
</code></pre>
<p>As you can see from line 6, all the props you passed in FormItem finally reached the actual input elements. But, <code>props</code> has more than input element needs. That’s why we use object destructuring on line 1 and remove <code>formik</code> and <code>options</code> from the props we pass to input element.</p>
<p>Now it’s time to use <code>formik</code> prop which we get with Formik’s <code>connect</code> method we used in FormItem component. <code>value</code>, <code>onChange</code>, and <code>onBlur</code> attributes are set to values/handlers provided by formik.</p>
<p>Almost done. The only thing left is the special handling of radio and checkbox. Let’s fill those parts in.</p>
<h3 id="handing-additional-props-for-radio"><a aria-hidden="true" tabindex="-1" href="#handing-additional-props-for-radio"><span class="icon icon-link"></span></a>Handing additional props for radio</h3>
<p>Each radio button has it’s own <code>value</code>. Since they share the same input name, form value is set to the value of the one user clicks. Browser uses <code>checked</code> attribute to decide whether it should be rendered as checked/unchecked. So, we set <code>checked</code> as true if the value of the radio button we’re rendering is equal to the value set in the form.</p>
<pre><code>if (props.type === 'radio') {
  props.value = option.value;
  props.checked = option.value === formik.values[props.name];
}
</code></pre>
<h3 id="handing-additional-props-for-checkbox"><a aria-hidden="true" tabindex="-1" href="#handing-additional-props-for-checkbox"><span class="icon icon-link"></span></a>Handing additional props for checkbox</h3>
<p>The default behavior for checkbox is usually not what web applications expect. If you have a group of checkboxes, and some of them are selected, your form values will be something like <code>{option1: true, option2: false, option3: true}</code>. But, most applications expect <code>['option1', 'option2']</code> as the value in their API. To achieve  this, we’ll override <code>onChange</code> method like below. Also <code>checked</code> attribute will rely on form value including the value of the checkbox being rendered.</p>
<pre><code>else if (props.type === 'checkbox') {
  props.value = option.value;
  props.checked = formik.values[props.name].includes(option.value);
  props.onChange = e => {
    const val = formik.values[props.name];
    e.target.checked
      ? val.push(e.target.value)
      : val.slice(val.indexOf(e.target.value));
    formik.setFieldValue(val);
  }
}
</code></pre>
<h2 id="putting-it-all-together"><a aria-hidden="true" tabindex="-1" href="#putting-it-all-together"><span class="icon icon-link"></span></a>Putting it all together</h2>
<p>Here is the full working example</p>
<div class="embed-container">
  <iframe width="100%" height="400" src="//jsfiddle.net/merictaze/vcaukthm/embedded/js,result/" allowfullscreen frameborder="0"></iframe>
</div>
<p>You can easily change the input components and make it work with react-bootstrap as below:</p>
<div class="embed-container">
  <iframe width="100%" height="400" src="//jsfiddle.net/merictaze/2jvcb87r/embedded/js,result/" allowfullscreen frameborder="0"></iframe>
</div>

Maybe you’re just getting started with distributed systems and system design, or you just need a quick recap for your upcoming interview. In either case, in this post, you’ll find the most common concepts of system design and the most important aspects of them. Let’s get started.

Recap of System Design Interview Concepts

Although what react is doing looks quite complex, underlying logic is very simple. And the easiest way to understand is just running some simple examples. We’ll dive into how react renders components and updates the actual DOM.

How React Rendering Works - A Step by Step Guide

DynamoDB is Amazon’s NoSQL database which offers single-digit milliseconds latency. It is great for variety of use cases, but when you need to run complex search queries on your dataset, you quickly realise it is not designed for it.

Indexing DynamoDB Items to ElasticSearch using AWS Lambda

Multitasking is the source of all evil. Until recently, I also liked having multiple screens and multi-tasking like many others. It was great to code on one screen while reading the slack messages and emails on the other screen. But, it was so easy to get distracted by continuous incoming notifications while trying to read, write or code something. Often, I was feeling tired in the middle of the day because continuous context switching was draining my energy and destroying my focus on the task I was working on. 

5 Tips To Stop Multitasking and Double Your Productivity

In this post, we are going to setup an environment with API Gateway, Lambda and DynamoDB using serverless framework which can be deployed to AWS directly or run fully local.

Going Serverless Offline

You solved 60 LeetCode hard and 300 LeetCode medium questions, you were a rockstar in your coding round and provided the most efficient solution in the world, but you couldn’t get the offer. Sounds familiar? Either case, keep reading, you might find some useful tips.

How to Succeed in Your Coding Interview

While making a simple request to https://google.com to see that simple search page, there are a lot of things going on behind the scenes to keep you secure. Understanding this flow will give you a lot of confidence in various topics like Digital Certificates and Signatures, Symmetric/Asymmetric key encryptions, Certificate Authorities and how they all work together to help you have secure communication.

What happens when you hit google.com using HTTPS

We are going to create a single component that supports text, textarea, select, radio, and checkbox. It will absorb all implementation differences for different inputs and will allow us using a unified component in our Formik forms.

Creating a unified Formik input field to support all input types seamlessly

System design questions can be asked for any level with different expectations from the candidate, but to get a Senior offer, you have to rock this round. Practice makes perfect - like for anything else, it applies for system design interview too. So, keep practicing without taking shortcuts, practice as if it’s the real interview and always follow the same steps to make it perfect.

How to Succeed in Your System Design Interview

Attacks like CSRF or XSS are still not clear to many of us. It is not because they are super hard to understand, but it requires some basic understanding of concepts like SOP, CORS, CSP, HTTPS. Let's start with what's Same-origin Policy