Element is, quite simply, an abstraction layer atop React.
You may find yourself asking, "Why an abstraction layer?". For a few reasons:
- In many applications, especially those extended by a rich plugin ecosystem as is the case with WordPress, it's wise to create interfaces to underlying third-party code. The thinking is that if ever a need arises to change or even replace the underlying implementation, it can be done without catastrophic rippling effects to dependent code, so long as the interface stays the same.
- It provides a mechanism to shield implementers by omitting features with uncertain futures (
- It helps avoid incompatibilities between versions by ensuring that every plugin operates on a single centralized version of the code.
wp.element global object, you will find the following, ordered roughly by the likelihood you'll encounter it in your code:
Install the module
npm install @wordpress/element --save
This package assumes that your code will run in an ES2015+ environment. If you're using an environment that has limited or no support for ES2015+ such as lower versions of IE then using core-js or @babel/polyfill will add support for these methods. Learn more about it in Babel docs.
Let's render a customized greeting into an empty element:
Refer to the official React Quick Start guide for a more thorough walkthrough, in most cases substituting
wp.element in code examples.
At the risk of igniting debate surrounding any single "best" front-end framework, the choice to use any tool should be motivated specifically to serve the requirements of the system. In modeling the concept of a block, we observe the following technical requirements:
- An understanding of a block in terms of its underlying values (in the random image example, a category)
- A means to describe the UI of a block given these values
At its most basic, React provides a simple input / output mechanism. Given a set of inputs ("props"), a developer describes the output to be shown on the page. This is most elegantly observed in its function components. React serves the role of reconciling the desired output with the current state of the page.
The offerings of any framework necessarily become more complex as these requirements increase; many front-end frameworks prescribe ideas around page routing, retrieving and updating data, and managing layout. React is not immune to this, but the introduced complexity is rarely caused by React itself, but instead managing an arrangement of supporting tools. By moving these concerns out of sight to the internals of the system (WordPress core code), we can minimize the responsibilities of plugin authors to a small, clear set of touch points.
While not at all a requirement to use React, JSX is a recommended syntax extension to compose elements more expressively. Through a build process, JSX is converted back to the
createElement syntax you see earlier in this document.
This assumes that you will import the
createElement function in any file where you use JSX. Alternatively, consider using the
@wordpress/babel-plugin-import-jsx-pragma Babel plugin to automate the import of this function.
Object that provides utilities for dealing with React children.
Creates a copy of an element with extended props.
?Object: Props to apply to cloned element
WPElement: Cloned element.
A base class to create WordPress Components (Refs, state and lifecycle hooks)
Concatenate two or more React children objects.
...?Object: Array of children arguments (array of arrays/strings/objects) to concatenate.
Array: The concatenated value.
Creates a context object containing two components: a provider and consumer.
Object: A default data stored in the context.
Object: Context object.
Returns a new element of given type. Type can be either a string tag name or another function which itself returns an element.
?(string|Function): Tag name or element creator
Object: Element properties, either attribute set to apply to DOM node or values to pass through to element creator
...WPElement: Descendant elements
This function creates an interpolated element from a passed in string with specific tags matching how the string should be converted to an element via the conversion map value.
For example, for the given string:
"This is a string with a link and a self-closing tag"
You would have something like this as the conversionMap value:
span: <span />a: <a href= '' />CustomComponentB: <CustomComponent />
string: The interpolation string to be parsed.
Object: The map used to convert the string to a react element.
WPElement: A wp element.
Creates a portal into which a component can be rendered.
- child (unknown type): Any renderable child, such as an element, string, or fragment.
HTMLElement: DOM node into which element should be rendered.
Returns an object tracking a reference to a rendered element via its
current property as either a DOMElement or Element, dependent upon the
type of element rendered with the ref attribute.
Object: Ref object.
Finds the dom node of a React component.
- component (unknown type): Component's instance.
Component enhancer used to enable passing a ref to its wrapped component.
Pass a function argument which receives
ref as its arguments,
returning an element using the forwarded ref. The return value is a new
component which forwards its ref.
Function: Function passed
ref, expected to return an element.
WPComponent: Enhanced component.
A component which renders its children without any wrapping element.
Checks if the provided WP element is empty.
*: WP element to check.
boolean: True when an element is considered empty.
Checks if an object is a valid WPElement.
Object: The object to be checked.
boolean: true if objectToTest is a valid WPElement and false otherwise.
Component used to detect the current Platform being used. Use Platform.OS === 'web' to detect if running on web enviroment.
This is the same concept as the React Native implementation.
Here is an example of how to use the select method:
;const placeholderLabel = Platform;
Component used as equivalent of Fragment with unescaped HTML, in cases where
it is desirable to render dangerous HTML without needing a wrapper element.
To preserve additional props, a
div wrapper will be created if any props
children are passed.
RawHTMLProps: Children should be a string of HTML. Other props will be passed through to div wrapper.
JSX.Element: Dangerously-rendering component.
Renders a given element into the target DOM node.
- element (unknown type): Element to render.
HTMLElement: DOM node into which element should be rendered.
Serializes a React element to string.
- element (unknown type): Element to serialize.
[Object]: Context object.
[Object]: Legacy context object.
string: Serialized element.
Component that activates additional checks and warnings for its descendants.
Switches the nodeName of all the elements in the children object.
?Object: Children object.
string: Node name.
?Object: The updated children object.
Removes any mounted element from the target DOM node.
Element: DOM node in which element is to be removed