App builder also provides the capability to build dashboard style applications. We can build single page applications using Visualforce pages and global actions to make app more interactive. Simply drag and drop the components into the builder layout to build the application. cmp resource and describes the design-time behavior of the Aura component-information that visual tools need to display the component in a page or app.Lightning app builder is a point and click tool to create a single page application for Salesforce1 and Lightning Experience. A design resource lives in the same folder as your. Well, let’s remember it. Design resource was used to control which attributes are exposed to builder tools like the Lightning App Builder, Community Builder, or Flow Builder. Ok, Do you remember using design resourcein Aura Component? When the component is selected on the page, the properties appear. Enables a component that includes configurable properties to be used on a Lightning community page in Community Builder. Used together with lightningCommunity_Page. Supports the target subtag.Įnables a component to be used on a Lightning page of type App Page.Įnables a component to be used on a Lightning Experience Home page.Įnables a component to be used on a Lightning record page.Įnables a component to be used on a Lightning community page in Community Builder. If you want your component to appear in the Lightning App Builder or in Community Builder, specify at least one Lightning page type. Targets:-Specifies which types of Lightning page the component can be added to. Do you remember using interface in Aura Components which enables to use of Aura Component with App page, Record Page, Home page or Community Builder? Migrate Interfaces:- The above image shows the interface counterpart in Lightning Web Component So, the same capability we have in Lightning Web Component, see how… If you do not use masterLabel tag in the configuration file, Your component name will default as the label of the component. Note:- Do not get confused with the Lightning Web Component name to be always as the label.
Appears in list views, like the list of Lightning Components in Setup, and in the Lightning App Builder and in Community Builder. To make a component usable in Lightning App Builder and Community Builder, set isExposed to true. To make a component usable in a managed package, set isExposed to true. Exposes the component in all orgs, and in Lightning App Builder and Community Builder. When you hover your mouse to the custom component deployed to the org, you can see the description with the label. Appears in list views, like the list of Lightning Components in Setup, and as a tooltip in the Lightning App Builder and in Community Builder. To check the current version, take help of this knowledge article.ĭescription:-A short description of the component, usually a single sentence. Cannot find Lightning Component Bundle Configuration File TagsĪpiVersion:- A double value that binds the component to a Salesforce API version. If you don’t include a configuration file for your component, you get an error similar to the following when you push your changes. What happens when you remove the configuration file from component’s project folder and tries to push it to your org? Include the configuration file in your component’s project folder, and push it to your org along with the other component files.
The configuration file follows the naming convention.
The configuration file defines the metadata values for the component, including the design configuration for Lightning App Builder and Community Builder.
0 kommentar(er)
