Read the blogpost I published in the Salesforce Developers blog.
Lightning Web Components is the new programming model that Salesforce released early this year. If you don’t know what it is about, check this post I published some time ago.
One of the keys to learn how Lightning Web Components work is to understand how components can communicate between each other. The communication patterns are different from Aura, and are one of the culprits of Lightning Web Components superb performance.Continue reading “Lightning Web Components Communication”
Same as Aura components, Lightning web components have a lifecycle managed by the framework. The framework is in charge of:
- In the creation phase, create the components, insert them into the DOM, and finally render them.
- In the destroy phase, remove them from the DOM.
You can check nice diagrams for both phases here.
During these phases, there are hooks that you can use, either to inject some extra code or to directly override the behaviour:
The 13rd of December this year, Salesforce announced the release of Lightning Web Components (LWC). This is something in which Salesforce has been working very hard, and which is surrounded by an aura of mystery. Because of that, in this blog I will try to explain the keys of this announcement.Continue reading “Lightning Web Components – and now what??”
When thinking about good quality software we must always have very present that tests automation is a must. There is a full list of tiers and tools that can be used to ensure that your software behaves as expected, bugs typically introduced by refactoring are prevented, and interconnected systems behave well together, as for example your code together with a Salesforce upgrade. In this post I want to focus on how to write unit tests for Lightning Components using Lightning Testing Service (LTS).Continue reading “Unit testing aura components with Lightning Testing Service and Mocha”