Lightning Components Developer’s Guide
jNewer Version Available
aura:dependency
The framework automatically tracks dependencies between definitions, such as components. This enables the framework to automatically reload when it detects that you've changed a definition during development. However, if a component uses a client- or server-side provider that instantiates components that are not directly referenced in the component’s markup, use <aura:dependency> in the component’s markup to explicitly tell the framework about the dependency. Adding the <aura:dependency> tag ensures that a component and its dependencies are sent to the client, when needed.
For example, adding this tag to a component marks the aura:placeholder component as a dependency.
1swfobject.registerObject("clippy.codeblock-0", "9");
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17<aura:dependency resource="markup://aura:placeholder" />The <aura:dependency> tag includes these system attributes.
| System Attribute | Description |
|---|---|
| resource | The resource that the component depends on. For example, resource="markup://sampleNamespace:sampleComponent" refers to the
sampleComponent in the sampleNamespace
namespace. Use an asterisk (*) in the resource name for wildcard matching. For example, resource="markup://sampleNamespace:*" matches everything in the namespace; resource="markup://sampleNamespace:input*" matches everything in the namespace that starts with input. Don’t use an asterisk (*) in the namespace portion of the resource name. For example, resource="markup://sample*:sampleComponent" is not supported. |
| type | The type of resource that the component depends on. The default value is COMPONENT. Use type="*"
to match all types of resources. The most commonly used values are:
Use a comma-separated list for multiple types; for example: COMPONENT,APPLICATION. |