#LIGHTNING PDF PROFESSIONAL 8 CODE#

In Aura we use can use one of two syntaxes, “”.Īlongside simply displaying pieces of data, we can also use conditionals and iterations to manipulate the final markup. The syntax differs between LWC, as do the capabilities. If we wish to express data within our HTML markup we need to use bind expressions. How can we express data into our HTML markup?

In Aura however, the “this” keyword does not point to the component context, instead we use the keyword from within our helper to reference other helper methods – this works for the same reason as in LWC, since the calling context is our helper.Ĩ.

#LIGHTNING PDF PROFESSIONAL 8 CODE#

Within LWC, the keyword can be used to access any component property or method – since “this” points to calling context of the current code – which in most cases will be from within the LWC. The “this” keyword can be found in both Aura and LWC, and their uses are quite similar. This means that an attribute of an LWC can hold any JavaScript data type – for example, we can hold all the standard data types, functions, HTML Nodes, Promises and anything else that we may require. In LWC, things are a lot more straightforward, since we do not need to define data types on our attributes. We can also define Aura attributes to hold SObjects and move advanced datatypes such as functions, Apex defined datatypes and we can define an attribute which can store other components. String, Boolean, Date, Object etc and arrays of those datatypes. Within Aura components we can use any of the basic data types, e.g. What data types can we use within Lightning components? Components can also be exposed as tabs or URL addressable for extra customisation.Īlongside the most common places mentioned above, there are some more niche places Lightning components can find themselves, including:ĭevelopment Basics 6. Lightning components can be used in a myriad of places, from drag and drop components making up Lightning App Builder pages, to quick actions launched via buttons on record detail pages. However, the opposite is not true, an LWC cannot be composed of Aura components, and they can only ever be its parent.Ĭode can also be shared between Aura and LWC components using an ES Module.ĥ. How do the two programming models coexist?Īura components can contain and utilise LWCs, including communicating with them via events and component methods. LWCs can only be developed using third party tools, which Salesforce recommends VSCode and their extension pack.Ĥ. How can we develop these components/what tools must we use?Īura components can be developed directly in Salesforce using the developer console, although third party IDEs (such as VSCode using SFDX) greatly improve developer efficiency. However, there are some scenarios where Aura components are still required, as of Summer ’21, these include building community templates and URL accessible components, although LWC is quickly reaching feature parity.ģ. Lightning Web Components should be the go-to approach for development due its increased performance, ease of development and alignment with modern web standards. Why would you choose one programming model over the other? The first is utilising the Aura framework to build out Aura components, the second is utilising the newer Lightning Web Components (LWC) framework.Ģ. There are 2 different programming models available for Lightning components. What are the different programming models available for Lightning components?

Lightning pdf professional 8