Assembly Line - abstraction used to connect multiple plugins to a base component.
Builder - term used to define a part of the code that received a chunk from the assembly line and uses it to generate code.
Chunk - term used to define syntax trees entities. Based on their type, they are fed to conde constructors.
Component UIDL - structure with multiple nodes that define a UI component.
Component Generator - aggregate that takes and UIDL structure and transforms it into code.
Component Node - object that describes how a component will look like when displayed.
Conditional Node - UIDL sub-structure used to define code inside conditional expressions.
Content Node - UIDL node that contains information about the displayed content of a component.
Dynamic Node - UIDL node type structure used to reference values that will supplied at run time by the generated code. Should be used to define the internal state of a component, props or even local variables.
Element Node - UIDL sub-structure used to represent visual elements.
Globals - node containing project specific information like general settings( i.e. language, title, etc ), specific asset information ( e.g.: style, script, icon, font, path ) or any other meta information needed for the project to run as wanted. Optionally, the node can contain information about the webapp manifest file.
Interface - refers to a TypeScript Interface that has the sole purpose of checking on the shape that values have.
Mapping - structure that associates an element of a given set with one or more elements of another set. The concept of element mapping comes from the need to generate code specific to components of various frameworks from UIDL definitions that are generic. Currently, in code generators there are HTML, React and VUE mapping structures that help with the translation from the UIDL specific key to a native one (e.g. a "click" event defined in UIDL component with be associated with an "onclick" event in HTML, "onClick" event in React or an "click" event in VUE).
Nested Style - section used to define responsive styles. This is not stable yet and is subject to changes in the near future.
Node Types - defines the type used for any section or a sub-section in an UIDL component. The type of the node can be any of the following: static, dynamic, conditional, element, repeat, nested-style, slot.
Plugin - code that adds a specific feature to an existing base component. In this generators, plugins are async functions that take as parameters a component UIDL structure and so specific operations. Some examples are here.
Project Generator - code base used to generate a complete functional project from an UIDL structure.
Prop Definitions - object defined inside a Component UIDL used by a parent component to pass values to its children. In order for a component to properly work, its props must be defined in the
propDefinition field. If a prop is used and it is not defined, the code generators will throw an error. If a prop is defined, but not used, the code generators will log a warning.
Repeat Node - UIDL node type used to define a repetitive structure (ex: v-for in Vue). Its purpose is to cover the mapping of multiple entities of the same type, usually provided in a data array, to a set of identical or similar visual elements.
Resolver - class instance that ensures the generic UIDL definitions are transformed into framework specific information.
Root Node - element of a Project UIDL structure containing information related to the entry point of the project. It defines a top-level routing mechanism. Its value is a component UIDL. Examples can be found here.
Routing - concept that refers to navigation from one page (or state) to another. Modern frameworks implement client side routing via their own libraries. In an UIDL project structure the routing mechanism is described inside
route field that can be defined in the
stateDefinitions node. More information and an example can be found here.
Slot Node - type of UIDL node used to specify where children passed from parents get to be placed in relation with other elements/children of the component. Currently, the code generators do not support name slots.
State Definitions - object defined inside a Component UIDL that contains key-value pairs used internally as state for that component. If a state is used and it is not defined in the
stateDefinition field, the code generators will throw an error. If a state is defined, but not used, the code generators will log a warning.
Static Node - UIDL node type used for static values (string or numbers). When this node type is used, the code generators passes the values as they are.
UIDL - abbr. for User Interface Design Language(UIDL), a standard representation for modern UIs. An UIDL is a structure that describes each element/component used in an UI. More details can be found here.
UIDL Node - the most basic building block in an UIDL structure. An UIDL Node contains information about a component used in an UI. When defined, it must contain information about
type must me a string and must be one of the following values -
nested-style. To learn how to declare a node check
Node Types section.
Validator - class instance that ensures the UIDL component and project definition is done properly. Currently, the validator not only ensures the provided JSON file has the correct format i.e. defined according to the latest UIDL schema, but also checks its content i.e. ensures no stateDefinitions, propDefinitions, local variables are used without being defined, no components are referenced without being defined in the project, component names are the same with than component keys referenced in the project, external dependency versions are consistent across the project, the
route state key is defined inside root, the first level children in the root component are conditionals based on the previously defined
route, prop and state key are not the same. Besides this, the validator will also give warnings if stateDefinitions, propDefinitions or local variables are defined but not used.