Book Image

Vuex Quick Start Guide

By : Andrea Koutifaris
Book Image

Vuex Quick Start Guide

By: Andrea Koutifaris

Overview of this book

State management preserves the state of controls in a user interface. Vuex is a state management tool for Vue.js that makes the architecture easier to understand, maintain and evolve. This book is the easiest way to get started with Vuex to improve your Vue.js application architecture and overall user experience. Our book begins by explaining the problem that Vuex solves, and how it helps your applications. You will learn about the Vuex core concepts, including the Vuex store, changing application state, carrying out asynchronous operations and persisting state changes, all with an eye to scalability. You will learn how to test Vuex elements and Vue components with the Karma and Jasmine testing frameworks. You will see this in the context of a testing first approach, following the fundamentals of Test Driven Development. TDD will help you to identify which components need testing and how to test them. You will build a full Vuex application by creating the application components and services, and persist the state. Vuex comes with a plugin system that allows programmers to extend Vuex features. You will learn about some of the most powerful plugins, and make use of the built-in logger plugin. You write a custom Google Analytics plugin to send actions to its analytics API, and an Undo/Redo plugin.
Table of Contents (8 chapters)

Developing an undo/redo plugin

The Google Analytics plugin we just coded is a good and simple example of how the Vuex plugin system can be exploited to add features to your application, without touching the application core code. But what about a more complex plugin? Is the Vuex plugin also suited for more complex operations? Well, of course, it is! In the following pages, we will develop an undo/redo plugin, which is still a simple, but not trivial example.

We can exploit the fact that, in using the Vuex system, we have a single centralized state and this state can only be modified by mutations. The idea is to take a snapshot of the state each time it gets modified. Then, to go back in the mutation history, it is enough to set the current state to a snapshot, representing an older state before the mutation occurred.

Let's start by creating a plugin that registers a module...