Jonathan Boiser jonboiser

Organizing Page States in Vuex Modules

Prior to this pull request, the pattern for rendering pages was as follows:

When browser goes to a route, the router executes a handler function (with a name like showClassesPage)
The handler will have some standard effects on the Vuex store (e.g. show loading page, update a pageName field that matches the route's name, etc.). It will usually request some data from the server and then terminate by committing a SET_PAGE_STATE mutation that copies that server data into Vuex inside of the pageState field.
The Vue component that is mapped to pageName will render and pull the data it needs to present from pageState.

After this Pull Request, this flow changes in the following manner:

	// - XState (all XState exports)
	const enterConfirmationStage = (context, event) => {
	context.atConfirmationStage = true;
	console.log(context)
	};

	const exitConfirmationStage = (context, event) => {
	context.atConfirmationStage = false;
	};

	from kolibri.core.auth.models import FacilityUser, Facility, Role
	from faker import Faker
	"""
	pip install Faker if you don't have it
	"""

	FAKE = Faker()


	"""

	"1-digit-multiplication-division"
	"1600s-1800s"
	"16th-18th-century"
	"1920s-america"
	"1950s-america"
	"1960s-america"
	"1970s-america"
	"1980s-america"
	"1990s-america"
	"19th-century"