Salesforce Lightning : A better way to handle component.find return value

I have always seen Salesforce Aura Component developers using multiple checks before fetching data from component.find method. It is because, it does return three types of results:

1. undefined – when there are no items found on the DOM
2. Single component – when there are only one item found in the DOM
3. Array of components – when there are more than an item found in the DOM

Salesforce Lightning : Device Based Behavior

Salesforce Lightning Components are a great way to build modern intuitive development. However, when there is a need for the component or the application to behave differently in different devices, we can make use of $Browser global value provider.

Salesforce Apex : URL Parameter Manager

To build endpoints, we often need a better method that is simplified and clean. With Salesforce PageReference class, it is easier for us to parse and build URL query string.

Salesforce : Detect change in Page URL

In Salesforce Lightning Community pages, we may have a logic that needs to be implemented in the Lightning Component when URL changes. This can be captured easily using forceCommunity:routeChange:

Salesforce Lightning : Get attribute of the elements – Event Handling

To get the attributes of elements that has been targeted (which element has been clicked), we can use two ways:

1. event.getSource()
2. event.target and event.currentTarget

Salesforce Apex : Dynamic SOQL Querying with uncertain relationship

Queries that involve complex relationship can be handled easily using List Methods.

Salesforce Lightning : Show or Hide a Modal

Modal popup can be added using SLDS as shown here.
It can be shown or hidden in two ways:

1. Using CSS Class
2. Using attribute variable