Lightning Components Developer’s Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Client-Side Processing for Component Requests

After the server processes the request, it returns the component definitions (metadata for the all required components) and instance tree (data) in JSON format.

The client performs these tasks:

  1. Deserialize the response to create a metadata tree.
  2. Traverse the metadata tree to create an instance tree.
  3. Traverse the instance tree to render the component.
  4. Render the components.

1. Deserialize the response to create a metadata tree.

The JSON representation of the component definition is deserialized to create a metadata structure (JavaScript objects or maps).

2. Traverse the metadata tree to create an instance tree.

The client traverses the JavaScript tree to initialize objects from the deserialized tree. The tree can contain:
  • Definition: The client initializes the definition.
  • Descriptor only: The client knows that definition has been pre-loaded and cached.

3. Traverse the instance tree to render the component.

The client traverses the instance tree to render the component instance. The reference IDs are used to recreate the component references, which can point to a ComponentDef, a model, or a controller.

4. Render the components.

The client locates the renderer definition in the component bundle, or uses the default renderer method to render the component and any sub-components.