Lightning Types Glossary of Terms

Learn more about the terms used in Lightning Types at Salesforce.

A template or blueprint for creating Apex objects. Use an Apex class to define the data structure (schema) for Custom Lightning Types.

A specific context or connection, such as lightningDesktopGenAi for the Agentforce panel, where you can override a custom Lightning type’s connections and the default UI. Different channels can have different editor.json and renderer.json configurations within the Lightning Type Bundle.

A specific type of renderer defined within renderer.json that uses the collection keyword to customize the display of a structured list or array of data.

A developer-created, JSON-based data type used to define a custom structure, validation, and user interface (UI) for complex data in Agentforce and other Salesforce applications.

The part of a Lightning Type that defines input UI components used to enter or edit data. In a Custom Lightning Type bundle, this configuration resides in editor.json.

A unique name that identifies a metadata component, often by combining a namespace with the component’s developer name. For example, the lightning:type keyword in schema.json uses an FQN to reference an Apex class, such as @apexClassType/c__AvailableFlight.

A standard specification used to define the structure, constraints, and validation rules for JSON data. The schema.json file in a Lightning Type Bundle uses this specification.

A reserved term in a schema.json file that defines a specific aspect of the data’s structure or validation rules. For example, title, properties, and lightning:type are keywords.

A JSON Schema-based data type used to structure, validate, and display data, consisting of a schema, an optional editor, and an optional renderer. Lightning Types include Standard Lightning Types and Custom Lightning Types.

See Standard Lightning Types and Custom Lightning Types.

The metadata component, with the API name LightningTypeBundle, used to create and deploy Custom Lightning Types. It’s stored in the lightningTypes folder and contains the schema.json file and, optionally, channel-specific folders with editor.json and renderer.json files.

A UI framework built on standard HTML, JavaScript, and CSS for creating custom user interface components on the Salesforce platform. Use LWCs to define the custom Editor and Renderer for Custom Lightning Types.

A Salesforce API used for retrieving, deploying, creating, updating, or deleting customization information, such as Custom Lightning Type Bundles.

A unique identifier used to distinguish metadata components. Use the default c namespace for components created in your org, or use the package’s namespace—for example, isv—for components from a managed package.

The part of a Lightning Type that defines the output UI component used to display data. In a Custom Lightning Type bundle, this configuration resides in renderer.json.

The part of a Lightning Type that defines the data’s structure and validation rules by using the JSON Schema specification. In a Custom Lightning Type bundle, this configuration resides in schema.json.

An out-of-the-box Lightning Type provided by Salesforce that includes a default schema, editor, and renderer. For example, lightning__textType and lightning__booleanType are standard Lightning types.