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.
Just passed the Community Cloud Consultant exam!
What I liked about this exam is that it forces you to look into functionality not commonly used within communities, such as topics or reputation and even moderation. It’s a valuable certificate to attain for opening your eyes to other areas of the platform you may not be so familiar with!
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.
A fantastic new feature in Summer ’17 release of Salesforce now allows you to define which unit tests can safely be run in parallel!
If you’ve disabled running parallel unit testing in your Salesforce org because of issues with concurrency (i.e. UNABLE_TO_LOCK_ROW exception) then this update is for you! You can still keep running of unit tests in parallel disabled, but you can now optionally indicate which unit tests can be run in parallel.
To do this, modify the annotation on your unit tests to include the following new parameter.
This should drastically speed up running of your unit tests in your Salesforce org! Find more on this in the Salesforce documentation:
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.
It’s finally generally available with the Spring ’17 release; the Apex stub API! This is really going to make your unit tests easier to write and enable you to write more meaningful tests.
In this post I’ll cover why this is such a big deal and how you can incorporate it into your unit tests going forward.
Visualforce got an update!
One of the coolest updates within the Spring ’17 release notes I found was the ability to now natively use the Lightning Design System directly inside Visualforce without needing to upload or reference a static resource.
Why is this cool? Simple. You don’t contribute to the overall limit of how much space your static resources take up and you benefit from always having the latest version of the Lightning Design System incorporated into your pages.
In this release Salesforce has added the new apex:slds tag.