If you’ve ever tried to build any kind of website, odds are you’ve had to create some way of validating and saving input from a form. Back in the bad old days this used to be a huge pain, because there were no good frameworks to help get the job done right. The three primary pain points that you have to deal with when trying to validate a form without the aid of a framework are:
* Pain Point #1. How to avoid writing a wall of if-statements for validating each data item
* Pain Point #2. How to handle adding and deleting data items as your code base evolves, i.e. how to avoid having to make changes in several different locations when you want to add/remove a data item
* Pain Point #3. How to display validation errors to your client
Thankfully there are now multiple frameworks available to help make the entire form process easier. But how do you decide which one to use for your shiny new web application? I’d personally recommend using the MEAN stack, because it addresses all three of the Pain Points listed above better than any framework I’ve ever worked with. You shouldn’t just take my word for it though, so we’ll start by walking through each Pain Point and why other solutions fall short in dealing with them. Then we’ll wrap up with a walkthrough of how to build some very reusable MEAN stack middleware and get you on your way toward implementing it.
Your new post is loading...
