Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore.

15 St Margarets, NY 10033
(+381) 11 123 4567



Storeon: An Event-Based State Manager for Velo

 Corvid changed its name to Velo.


In the article, “State management in Corvid,” Shahar Talmi brings up a question about controlling app states in Velo. If you’re not familiar with Velo, it’s a development platform running on Wix that allows you to quickly and easily develop web applications.

Accurately controlling the state of any app is a really big problem. If you have many component dependencies or need to handle constant user interactions, you’re going to suffer a bit when you want to eventually add a new feature or scale your application.

In this article, I share my solution — a very tiny library called Storeon (it’s only 180 bytes) that features an easy interface. So, I wrote a wrapper for integration with Velo. As a result, we have the state manager storeon-velo, and it’s less than 90 lines of code.

You may also like: Angular Tutorial: State Management With NgRx.

How it Works

We will create a traditional study app with counters. I will use two counters to help provide a better demonstration.

At first, we need to install the library from Package Manager.

Package Manager panel in Wix editor, installing storeon-velo

Then, we can create one more file for store initialization in the public folder.

We will write our business logic in the public/store.js file.

Storeon’s state is always an object; it canʼt be anything else. Itʼs a small limitation and not too important to us, but we have to remember it.


So, we created a store in the public folder and exported from there with four methods. In the second part, we will create our UI, and we will write logic to change the state. 

Letʼs add two text elements to display our counter value and four buttons for event increments/decrements.

Creating two counter components

Creating two counter components

Of course, we have to import the store methods from the public file to the page’s code:

import { dispatch, connect, connectPage } from 'public/store'; 

With connect("key", callback), we can subscribe to any store properties, and the callback function will run when the page is loaded and each time the listed property changes.

The connectPage(callback) is a wrapper around $w.onReady(callback). With dispatch(event, [data]), we will emit events.

Page Code



The function, createStore(modules), accepts a list of modules. We can create different functions to split business logic into our app. Letʼs look at a few examples.

Example 1: Synchronization in the app state with the wix-storage memory API:

Example 2: Tracking an event to external analytics tools with wixWindow.trackEvent():

Example 3: Combining modules:


As you can see, we were able to quickly implement our state management solution with a minimal amount of code. Of course, due to data binding in Velo, you normally don’t have to worry about state management. However, in more complex applications, the issue can become more difficult, and state management will become more challenging to handle.

State management can be a tricky problem, but Storeon offers a simple, yet robust solution. In addition, Velo allows us to quickly implement this in our application, all while focusing on code and not having to spend time dealing with other issues. 



Further Reading

This article originally published on https://shoonia.site

Credit: Source link

Previous Next
Test Caption
Test Description goes like this