Book Image

Building Forms with Vue.js

By : Marina Mosti
Book Image

Building Forms with Vue.js

By: Marina Mosti

Overview of this book

Almost every web application and site out there handles user input in one way or another, from registration forms and log-in handling to registration and landing pages. Building Forms with Vue.js follows a step-by-step approach to help you create an efficient user interface (UI) and seamless user experience (UX) by building quick and easy-to-use forms. You’ll get off to a steady start by setting up the demo project. Next, you’ll get to grips with component composition from creating reusable form components through to implementing the custom input components. To further help you develop a convenient user input experience, the book will show you how to enhance custom inputs with v-mask. As you progress, you’ll get up to speed with using Vuelidate and Vuex to effectively integrate your forms. You’ll learn how to create forms that use global state, reactive instant user input validation and input masking, along with ensuring that they are completely schema-driven and connected to your application’s API. Every chapter builds on the concepts learned in the previous chapter, while also allowing you to skip ahead to the topics you’re most interested in. By the end of this book, you will have gained the skills you need to transform even the simplest form into a crafted user and developer experience with Vue.
Table of Contents (15 chapters)
Title Page

Translating the API into a working schema

Now that we have our mock API running, the next step is to create a way for our application to parse or translate this API structure into the schema structure that we had before, and that it understands. If you are curious enough to try to run the application at this point, you will encounter a ton of console errors that yell at you about prop: type check failed and v-model failing to bind. This is expected at this point.

Go ahead and create a new folder inside src; we are going to call it libraries. This is not a strict naming convention, so feel free to name it whatever makes more sense to you or your team. Inside this folder, we are going to make a new file called Api.js. Our goal for this file is to put all of the code that handles the parsing of the API schema into the app's schema here. This way, we can import whatever we need...