Last Updated on April 15, 2022 by Rakesh Gupta
The Lightning Component modern framework is a User Interface framework to develop dynamic web apps for mobile and desktop devices. As is the case with each release, the latest Spring‘19 release is packed with rich features including, the newly added Lightning Component features!
Currently, Spring’19 release is available under the pre-release program. Sandboxes will be upgraded on 4th and 5th of January. As a result, your organization will get the look and feel of Spring’19 release.
In case you have not read the entire 429 pages of Salesforce Spring’19 release notes, check out Spring’19 release quick summary and the Spring into Top 10 Lightning Experience Gems of Salesforce Spring’19 Release! written by me.
I combed through the release notes and highlighted the added capabilities to the Lightning Component features. Believe me, it was hard to stop at just five! To kick things off, here is my take on the coolest Lightning Component features from Spring’19 release.
1) Lightning Web Components (Generally Available):- Now you can build Lightning components using two programming models: Lightning Web Components, and the original model, Aura Components. Lightning web components are custom HTML elements built using HTML and modern JavaScript. Lightning web components and Aura components can coexist and interoperate on a page. To admins and end users, they both appear as Lightning components. To learn more about Lightning Web Component click here.
Lightning Locker supports the new Lightning Web Components programming model.
2) Get Notified About Unsaved Changes:- Notify the UI about unsaved changes in your component with the lightning:unsaved Changes Aura component. You can use lightning:unsavedChanges in standard and console navigation apps. You can then use a controller to save or discard the changes.
3) Reference Asset Files with the $ContentAsset Global Value Provider:- The $ContentAsset global value provider lets you reference images, style sheets, and JavaScript used as asset files in your Lightning components. Reference $ContentAsset asset files by name instead of using cumbersome file paths or URLs. $ContentAsset provides sharing, versioning, and access control for all asset files, as well as options for mobile optimization and resizing of image files. You can use $ContentAsset in Lightning components markup and within JavaScript controller and helper code.
4) Add Region Labels to Your Aura Page Template Components:- As part of the new template switching feature in the Lightning App Builder, you can now add labels to each region in your Aura page template components. These labels appear in the template switching wizard in the Lightning App Builder when users map region content to a new template.
In the design file for your component, add the label attribute to the flexipage:region tag like this:
<design:component label="Two Region Custom App Page Template"> <flexipage:template > <!-- The default width for the "left" region is "MEDIUM". In tablets, the width is "SMALL" --> <flexipage:region name="left" label="Left Region" defaultWidth="MEDIUM"> <flexipage:formfactor type="MEDIUM" width="SMALL"/> </flexipage:region> <flexipage:region name="right" label="Right Region" defaultWidth="SMALL"/> </flexipage:template> </design:component>
Region labels are supported only in Aura components that implement one of these interfaces:
- lightning:appHomeTemplate
- lightning:homeTemplate
- lightning:recordHomeTemplate
5) Navigate to a URL with the standard__webPage Page Reference Type:- The navigation service uses a PageReference object to describe pages. A new PageReference type of standard__webPage wraps a raw URL so that you can navigate to external websites.
Note: – You can download release notes in HTML format!, for PDF file.
What are your favorite Spring’19 release note gems? Care to share?
Your Blog is very useful indeed for better understanding about Salesforce Lightning Component please visit
Be sure to read ALL the many places where you cannot use Lightning Web Components! I was disappointed for example that they cannot be used with the new Lightning Console or in Lightning Out Components (the last one must be wrapped in an Aura Component). The list is much longer than this.
I know its a separate team that worked on this, but when is Salesforce going to provide native Object Level and Field Level Security support? To me, this is a glaring omission for Lightning Components that many Orgs do not go to the trouble of creating a service to provide (ISV’s must implement one to pass security review). There’s an obvious need for this from a company where Security is their number one priority, I do not understand this.