Development questions
Why can renderedCallback run multiple times and how do you prevent repeated execution?
DevelopmentMedium
renderedCallback fires after every render, and any change to a reactive property used in the template triggers a re-render. Also, it runs for each component in the tree.
Pitfalls: one-time setup (loading a library, attaching listeners) would repeat, and changing a reactive property inside it can cause an infinite render loop.
Fix: use a guard flag:
javascript
renderedCallback() {
if (this.initialized) return;
this.initialized = true;
// one-time DOM work
}
Put data loading in connectedCallback and avoid setting tracked state in renderedCallback unless guarded.
lwclifecyclerenderedcallback
More Development questions
- What is an Apex Trigger in Salesforce and when should you use it over Flows?
- What is the difference between before triggers and after triggers?
- Explain all Trigger context variables (isInsert, isUpdate, isDelete, isUndelete, isBefore, isAfter, isExecuting, size, operationType).
- What is the difference between Trigger.new and Trigger.old?
- In which trigger events are Trigger.new and Trigger.newMap available?
- In which trigger events are Trigger.old and Trigger.oldMap available?