Book Image

Hands-On Full Stack Web Development with Aurelia

By : Diego Argüelles Rojas, Erikson Murrugarra
Book Image

Hands-On Full Stack Web Development with Aurelia

By: Diego Argüelles Rojas, Erikson Murrugarra

Overview of this book

Hands-On Full Stack Web Development with Aurelia begins with a review of basic JavaScript concepts and the structure of an Aurelia application generated with the Aurelia-CLI tool. You will learn how to create interesting and intuitive application using the Aurelia-Materialize plugin, which implements the material design approach. Once you fully configure a FIFA World Cup 2018 app, you'll start creating the initial components through TDD practices and then develop backend services to process and store all the user data. This book lets you explore the NoSQL model and implement it using one of the most popular NoSQL databases, MongoDB, with some exciting libraries to make the experience effortless. You'll also be able to add some advanced behavior to your components, from managing the lifecycle properly to using dynamic binding, field validations, and the custom service layer. You will integrate your application with Google OAuth Service and learn best practices to secure your applications. Furthermore, you'll write UI Testing scripts to create high-quality Aurelia Apps and explore the most used tools to run end-to-end tests. In the concluding chapters, you'll be able to deploy your application to the Cloud and Docker containers. By the end of this book, you will have learned how to create rich applications using best practices and modern approaches.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Foreword
Contributors
Preface
Index

Improving our application forms – Validators


We know how the binding engine of Aurelia works. Also, we know how to intercept and customize that binding behavior. We know too how to transform data between View-ViewModel layer according to our needs. Just some things are pending, and the aurelia-validation plugin is one of them. When you need data provided by the user, you have to expect anything. The user didn't know your app. He will do anything he wants, and you need to be prepared for that. You need to ensure that data provided by the user is, at least, in the right format your back service is expecting. You need to filter just the right values and send alerts to the user telling which values are wrong and how they can fix it. We often need to put ourselves on the user's side. Software development is more than just programming, more than just creating forms and storing/retrieving data. We need to make our application fault-tolerant and as we said earlier, think always in the worst case...