Optional
appendedThis method operates on a just appended child node. As it is called while processing the parent node, the source node reference in context refers to the original representation of the parent node.
Note that while in general parent
should be of type ParentNode
and
child of type ChildNode
, previous processing may have provided a
different state. Thus, you may require applying corresponding type
checks first.
Optional
idOptional ID for a given configuration. Possibly useful for debugging purpose.
Optional
importedThis method operates on a just imported node to the target document. It is neither attached to DOM and does not contain any child nodes.
Note, that information provided via context (such as the original source node) must not be manipulated.
Also note that previous processing may have already adapted or even exchanged the imported node. So, it may make sense to do some checks on the original node instead, like, if a given rule is applicable.
Typical behaviors done at this stage:
You may also append child nodes in this state. Original child nodes will
then be appended. Nevertheless, structural changes are best applied
in the importedWithChildren
step, as you have full control of the
structure then.
Alternative to this, you may add children to the original
DOM as part of the prepare
step.
Optional
importedThis method operates on an imported node to the target document. While it is not attached to DOM yet, children already got converted and appended.
Note, that information provided via context (such as the original source node) must not be manipulated.
Also note that previous processing may have already adapted or even exchanged the imported node. So, it may make sense to do some checks on the original node instead, like, if a given rule is applicable.
Optional
prepareThis method may operate on the source node prior to importing it into
the target document. This may be useful if the source API is richer
than available later in processing. Like, for to data mapping, the data
view may contain HTMLElement
providing access to HTMLElement.dataset
,
while the XML element in the target document later is a raw Element
.
Note that some limitations apply to actions performed in this stage:
Thus, it is safe, for example, to add or remove child nodes or attributes in this stage.
Optional
priorityPriority in which the given rule section is executed.
Defaults to priority normal
.
A configuration for either
toData
ortoView
transformation.While processing, the following steps will be sequentially invoked for a given node:
Note that for a given node, first all
prepare
steps are executed for a given node, then allimported
steps, and so on. Thus, do not expect by default that a node handled inprepare
step comes unchanged to the next step imported.