Maquette itself is not a framework.
This means it does not force you to structure your application in a certain way.
Using components however is an obvious and convenient way to structure your application.
A component by convention an object instance with a
This method can then be called a parent component in their
thus forming a simple component hierarchy.
The code below shows this mechanism in its simplest form; the
okButton component is used in the
Let us go one step further and create a function that can produce configurable button components.
There is one problem however with the implementation we have just shown. Consider the following snippet:
If the user presses the next button, the next button should disappear and the finish button should appear. However, if you press the next button now the application event throws an error (check your browser console). This is because maquette does not see one button disappearing and another button appearing, it sees a button changing its text and the onclick handler. And changing an event handler is prohibited in maquette, hence the error.
We want maquette to recognize that one button disappears and another button appears.
Not only to prevent the error, but also because it allows us to use the right animation.
In order to make maquette recognize that the button did not change but got replaced by another button you need to
provide a unique
key property. The best value for the key property is probably the component instance itself.
In code below you see
myButton used as a
key for the component instance:
In this snippet we did something else as well. We added an extra wrapper element
my-button, which has a nonstandard tagname.
This technique is also used by other frameworks, like polymer. This makes styling and debugging your components easier.
Browsers will just use an HTMLUnknown element which essentially just works just like a <span>.
You can decide for yourself if you also want to use this.
You can continue reading how to unit test components.