data-tier

Summary

DataTier ('tier' from 'to tie') is a service oriented framework, that provides two way binding (Model-View - View-Model, aka MVVM) in the domain of client HTML/Javascript applications. This library works tightly with Observable-driven event cycle, therefore it comes with an embedded object-observer.js library.

Yet, it is possible to provide any other Observable implementation, if it provides the same functionality. In this case you may want to use lighter data-tier distribution (bundled within the same npm module) without object-observer.js.

Support matrix: ₄₉₊, ₄₄₊, ₁₃₊

Support matrix is currently as wide as that of object-observer.js, assuming that in most of the cases consumers will not provide their own object observer, but will use an embedded one. DataTier supports custom elements as well, obviously this functionality is available only on supporting environments.

Versions

• 0.6.10

  • Added a possibility to create/update Tie's data with a plain JS object, in this case DataTier will attempt to auto-create and use Observable from it, using an embedded Observable implementation
  • Fixed issue no. 7

• 0.6.9

  • Conceptually Rule has been replaced by Controller. There are still no API changes with regard to that, nor any API are yet published, but there will be some refactoring in this area in future releases
  • Fixed issue no. 6, some performance improvements made for a large scale DOM manipulations

• 0.6.8

  • Fixes: issue no. 2 (smooth handling of an empty values given to the controllers definition), issue no. 4 (non working repeaters on subgraph list), issue no. 5 (improvements of data-tie-classes)

• 0.6.7

  • Added a possibility to create a tie without providing any initial data, for early setup with lazy data provisioning

• 0.6.5

  • Fixed a case that element having no dataset breaks the views collection flow (this is not a valid case, but see this issue in Edge, so got to be defensive here)
  • Added tieSrc rule and removed obsolete tieImage rule (did the same as tieSrc, just in a less general flavor)
  • Added tieHRef rule
  • Added tieClasses rule

• 0.6.0

  • Moved to object-observer.js library as an observation engine, were impacted both the API and the implementation.

• 0.5.41

  • First version, based on native Object.observe technology.

Loading the Library

You have 2 ways to load the library: into a window global scope, or a custom scope provided by you.

• Simple reference (script tag) to the data-tier.js in your HTML will load it into the global scope:

<script src="data-tier.js"></script>
<script>
	let person = { name: 'Uriya', age: 8 },
	    observablePerson = Observable.from(person);
	DataTier.ties.create('person', observablePerson);
</script>

• The snippet below exemplifies how to load the library into a custom scope (add error handling as appropriate):

let customNamespace = {},
    person = { name: 'Nava', age: 6 },
    observablePerson;

fetch('data-tier.js').then(function (response) {
	if (response.status === 200) {
		response.text().then(function (code) {
			Function(code).call(customNamespace);
			
			//	the below code is an example of consumption, locate it in your app lifecycle/flow as appropriate
			observablePerson = customNamespace.Observable.from(person);
			customNamespace.DataTier.ties.create('person', observablePerson);
		});
	}
});

• Note the usage of an embedded Observable along the way. As it has been mentioned before, you may provide your own Observable implementation and in this case more lightweigth data-tier-wo-oo.js will suite you more.
• Minified version is also available for both distributions, with and without object-observer.js.

Base concepts

The library utilizes 2 main concepts Ties and Controllers.

Tie

Tie holds an observable data structure (object or array) associated with tie's name, it's about what to tie. Thus, ties serve most and foremost data segregation and management purposes.

Data within a tie is referenced by path: dot (.) separated keys along the object's hierarchy where in case of arrays index being the key. Consider the following data structure:

let bands = [
	{
		id: 1234,
		name: 'Dream Theater',
		since: 1985,
		albums: [
			{ id: 2345, name: 'When Dream and Day Unite', since: 1988 },
			{ id: 2346, name: 'Images and Words', since: 1991 }
		]
	}
];
bands.totalTooltip = generateTooltipText();

Now one can create a tie named 'bandsTie' and set its data to be (an observable clone of) the bands array. Having that, any UI element would be tied to this dataset via the tie name and the path:

• bandsTie.0 - refer to the whole object at index 0 of our array
• bandsTie.length - length property, inherited from the native Array, may also be used
• bandsTie.0.name - path can get deeper...
• bandsTie.0.albums.1.since - ...actually, it can get to any level of deepness

Important: the first item in the path is always the tie's name.

Basically, it is possible to create a single dataset for the whole application, making a single 'uber-tie' from it and operating everything from there, but it should be considered as a bad practice. Having say that, I'll note, that there is no limitations on the size or the structure complexity of the tied model, nor there are any negative effects of those on application performance.

Tie object not only meant to hold the link between the data and its namespace, but also tie's specific configurations and customizations. Currently in the backlog there are such a features like supporting custom interceptors for both flows - data-to-view and view-to-data. Those features are under ongoing development and enhancements. For more details see API reference.

Controller

Controller is a holder of transition logic, it's about how to translate the data from/to view/data.

Each controller has it's own unique name given to it upon registration. Controllers are applied via the DOM's data-* attributes joining the data- prefix with rule's name: data-tie-text applies the controller 'tieText'. Let's see the following example:

<span data-tie-text="bandsTie.length"
	  data-tie-tooltip="bandsTie.totalTooltip">
</span>

<div>
	<template data-tie-list="bandsTie.0.albums => album">
		<span data-tie-text="album.name"></span>
	</template>
</div>

In the first part we tie between the span (view) and the model (we have tied it to both, length and totalTooltip values), while using 2 controllers to say, how the value will be visualized. Attributes' values (bandsTie.length, bandsTie.totalTooltip) are controllers' configurations for this specific instance and their syntax/content is part of each rule's API. In most cases the tie name and the path to the data would be sufficient, but conceptually rule's configuration may be anything rule needs.

Thus, in the second part a template element tied by a 'tieList' rule. This rule expects more rich content in its configuration: tie name and path for sure, but also some name for an item within iteration (here - 'album', and see its usage in the inner span element).

There is a set of controllers bundled with the library, they are described in the Controllers reference. This set will eventually be updated and enhanced upon a needs and feedbacks from real world usages. But even more important is the fact, that controllers may be created and added by a consuming application. This can be done at any phase of application's lifecycle, so there is no special ceremony around it whatsoever. Controllers management described in the relevant section in API reference.

Basic example

In essence, the purpose of the DataTier service is to tie model and view and sync between them automatically once changes detected in either one or another.

In order to make this happen, two things need to be done:

• any model to be shown should be registered in the DataTier service
• DOM elements intended to visualize the model need to be decorated with an appropriate declaration

The above two may happen in any order, in any phase in the application lifecycle. DataTier supports lazy binding, watching for DOM changes as well as for a data changes and will pick up any new linking information relevant and tie the things up.

Let's review the actual example, where we have some user object which is our model and we want to bind it to some interactive view of it.

Code part

let user = {
	name: 'User Name',
	age: 7,
	active: true,
	address: {
		street: 'Some street',
		apartment: 15
	}
},
observableUser = Observable.from(user);

DataTier.ties.create('userInfo', observableUser);

HTML part

<div>
	<span data-tie-text="userInfo.name"></span>
	<span data-tie-text="userInfo.age"></span>
	<input type="checkbox" data-tie-value="userInfo.active">
	<div>
		<input type="text" data-tie-value="userInfo.address.street">
		<input type="text" data-tie-value="userInfo.address.apartment">
	</div>
</div>

Documentation

Tutorials page.

API Reference page.