In my previous blog post I promised (pun intended) to walk you through how to implement JavaScript Promises within Lightning Components and discuss how they can help simplify managing asynchronous callbacks.
Continue reading “Using JavaScript Promises within Lightning Components”
In todays post, I will be walking you through Lightning Component Methods (a.k.a. Aura Methods) and how they can benefit your applications by simplifying the development process and maximising code reuse.
A really useful plugin for hiding away all of the metadata XML files whilst you’re developing in Sublime 3 is ToggleExclude. Check out the package listing over on PackageControl.io to see how it can really help with helping you focus on the files which matter when developing.
https://packagecontrol.io/packages/ToggleExclude
Below is my configuration file for hiding away Apex class, Trigger, Visualforce Page, Visualforce Component and Lightning Component metadata files.
{
"conditional_file_exclude_patterns": [
"*.cls-meta.xml",
"*.component-meta.xml",
"*.page-meta.xml",
"*.trigger-meta.xml",
"*.cmp-meta.xml"
],
"enabled": true
}
In this blog post I’m going to show you how to increase the usability of your Lightning Components in your application by decoupling responsibilities and enforcing separation of concerns.
Continue reading “An approach to reusing Lightning Components”
One thing I hear from time to time is that Lightning Components can be a little slow, especially when rendering dynamic data. In this blog post I’m going to share some thoughts and approaches on how to speed up rendering times and improve the usability of your applications.
The problem
Sometimes it can be a little frustrating when developing Lightning Components because you want to follow the DRY principle (Don’t Repeat Yourself) because the framework does not yet offer a suitable way of accessing a shared library of code. There is a solution available in the open source version, but it’s not yet available on the platform.
Continue reading “Sharing JavaScript code across Lightning Components”
As developers we are frequently capturing data from form input, validating and displaying errors back to the user when validation criteria are not met. Other times we have to create strings such as URL’s with dynamic parameter values or even queries with dynamic where clauses.
In this blog post I want to demonstrate a much better approach on how to create dynamic error messages or even other types of strings using the under used String.format method.
Quirky Apex 