Heroku is a PaaS (Platform as a Service) that allows to build and run web apps, jobs and APIs in 8 languages, while the platform takes care of things like routing, erosion or failures for you. When using Heroku, you can utilize add-ons that will make your life easier, to create and use databases, handle deployments, manage logging etc., among other features, making the tasks of building, deploying and running apps a much pleasant experience.Continue reading “Understanding Heroku Git deployments”
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”
If your company has offices in different locations I am sure you have heard about Translation Workbench. Translation Workbench is a tool that allows you to translate Salesforce texts to different languages. In this post I want to dig into how translations are implemented in the system, and how to work with them through the metadata API.
Lightning Pages are a concept introduced by Salesforce to allow creating and customizing pages in Salesforce with simple drag & drop, for Lightning Experience and Salesforce1. In this post I want to explain how these pages behave in a managed package environment.
Last week I discovered something about Lightning Components I didn’t know about: aura:action. This is an attribute type that you can use to pass actions to a child component, in addition to the other supported attribute types, and it can be specially helpful if you want to decide at component instantiation which actions should the child component perform.
When working with Lightning Components framework it is very important to understand how the different components are rendered by the framework, which possibilities do we have to interact with the component lifecycle and how will the framework react to certain events as for example a change of an attribute. Want to know more? Continue reading!
A typical use case when creating records is to populate some fields in advance, and then let the user fill in the rest of required fields. Let’s say that we want to create account records, having a pre-populated description, like this: