Book Image

Learning Salesforce Lightning Application Development

By : Mohit Shrivatsava
Book Image

Learning Salesforce Lightning Application Development

By: Mohit Shrivatsava

Overview of this book

Built on the Salesforce App Cloud, the new Salesforce Lightning Experience combines three major components: Lightning Design System, Lightning App Builder, and Lightning Components, to provide an enhanced user experience. This book will enable you to quickly create modern, enterprise apps with Lightning Component Framework. You will start by building simple Lightning Components and understanding the Lightning Components architecture. The chapters cover the basics of Lightning Component Framework semantics and syntax, the security features provided by Locker Service, and use of third-party libraries inside Lightning Components. The later chapters focus on debugging, performance tuning, testing using Lightning Testing Services, and how to publish Lightning Components on Salesforce AppExchange.
Table of Contents (22 chapters)
Title Page
PacktPub.com
Foreword
Contributors
Preface
Index

Understanding attributes


Let's understand value providers in Lightning Components, before diving deeper into attributes. Value providers hold data and provide a way to access that data. Lightning Components have two types of value providers out of the box. They are listed in the following table:

Value provider

Description

v  (view)

This allows access to the value of the attribute in the Component Markup.

c  (controller)

This allows you to wire events and actions .

 

An attribute is a placeholder to hold data. You can treat attributes like Java variables. The following is the syntax to define attributes:

<aura:component>
    <aura:attribute name="searchString" type="String" default="lighnting components"/>
</aura:component>

Name and data type are mandatory when defining attributes. An attribute can be one of the following types: primitive (string, integer, decimal, Boolean, double, date, dateTime), arrays (sets, list, maps), objects, custom Apex, functions, or Salesforce sobject....