Lightning Aura Components Developer Guide

Introducing Aura Components
Quick Start
Creating Components
Component Names
Create Aura Components in the Developer Console
Create Aura Components Using Salesforce CLI
Component Markup
Component Namespace
Using the Default Namespace in Organizations with No Namespace Set
Using Your Organization’s Namespace
Using a Namespace in or from a Managed Package
Creating a Namespace in Your Organization
Namespace Usage Examples and Reference
Component Bundles
Component IDs
HTML in Components
CSS in Components
Component Attributes
Using Expressions
Component Composition
Component Body
Component Facets
Controlling Access
Using Object-Oriented Development
Best Practices for Conditional Markup
Aura Component Versioning for Managed Packages
Base Components with Minimum API Version Requirements
Validations for Aura Component Code
Using Labels
Localization
Working with Lightning Base Components
Supporting Accessibility
Writing Documentation for the Component Library
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Testing Components
Debugging
Performance
Reference
PDF

Using Your Organization’s Namespace

If your organization has set a namespace prefix, use that namespace to reference components, events, custom objects and fields, and other items in your Lightning Lightning markup.

The following items use your organization’s namespace when your organization has a namespace prefix set.

  • References to components that you’ve created
  • References to events that you’ve defined
  • References to custom objects
  • References to custom fields on standard and custom objects
  • References to Apex controllers
  • References to static resources

Support for the c namespace in organizations that have set a namespace prefix is incomplete. The following items can use the c namespace if you prefer to use the shortcut, but it’s not currently a recommended practice.

Note

  • References to components that you’ve created when used in Lightning markup, but not in expressions or JavaScript
  • References to events that you’ve defined when used in Lightning markup, but not in expressions or JavaScript
  • References to custom objects when used in component and event type and default system attributes, but not in expressions or JavaScript

See Namespace Usage Examples and Reference for examples of the preceding items.