... | ... | @@ -62,7 +62,11 @@ Configures input search fields to be displayed on the authority maintenance tab |
|
|
Configures the elasticsearch search routes for each resource type along with which indexed document's fields to query for and which fields to show in result list.
|
|
|
|
|
|
### State model
|
|
|
The state of the application is held in a set of object structures under the control of the Ractive.js instance. The most important part of the structure is the `inputGroups`, which is derived from the `tabs` array in the configuration. Accessing the model is done via `ractive.get()` function with a path as argument, e.g. `ractive.get('inputGroups.1.inputs.3')` which retrieves the fourth input of the second tab. Each input again has a `values` array, each having a `current.value` and `old.value`. When values are changed, a patch is generated based on difference between a value's old and current value. The patch is then sent to back end as a `HTTP PATCH`.request Values representing a link to another resource has in addition a `displayValue` field, showing the name or a more user friendly representation of the linked resource.
|
|
|
|
|
|
### Partials
|
|
|
Even if the application's main engine is a massive block of code, the user interface is divided into a number of parts, called partials in Ractive.js lingo. Partials feed on the context in which they are invoked, such as an `input` node as the example above.
|
|
|
|
|
|
### Decorators
|
|
|
|
|
|
# Development
|
... | ... | |