Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
Lightning Components are a powerful way to build custom user interfaces for Salesforce applications. However, there are different execution modes for Lightning Components, and it's important to understand the differences between them so that you can choose the right mode for your needs.
In this blog post, we'll discuss the two main execution modes for Lightning Components: debug mode and production mode. We'll also cover some of the pros and cons of each mode, so that you can make an informed decision about which mode to use for your components.
Debug Mode
Debug mode is the default execution mode for Lightning Components. It's designed to make it easier to debug your components by providing more detailed error messages and logging output. In debug mode, the JavaScript source code for your components is not minified, which makes it easier to read and understand.
Debug mode also includes some features that can help you track down errors in your components. For example, you can use the console.log() function to output messages to the browser console, and you can use the debugger statement to break execution of your code at a specific point.
Production Mode
Production mode is the mode that you should use for your components when they are deployed in production. In production mode, the JavaScript source code for your components is minified, which makes it smaller and faster. Minifying the code also makes it more difficult to read and debug, so you should only use production mode once you are confident that your components are working correctly.
In addition to minifying the code, production mode also disables some of the features that are available in debug mode. For example, the console.log() function and the debugger statement are not available in production mode.
Choosing the Right Execution Mode
So, which execution mode should you use for your Lightning Components? The answer depends on your needs. If you are still developing your components and you need to be able to debug them easily, then you should use debug mode. However, if your components are deployed in production and you need to improve their performance, then you should use production mode.
Here is a table that summarizes the pros and cons of each execution mode:
|
Execution Mode |
Pros |
Cons |
|
Debug Mode |
* Easier to debug |
* Code is not minified, which makes it larger and slower |
|
Production Mode |
* Code is minified, which makes it smaller and faster |
* More difficult to debug |
Conclusion
In this blog post, we discussed the two main execution modes for Lightning Components: debug mode and production mode. We also covered some of the pros and cons of each mode, so that you can make an informed decision about which mode to use for your components.
I hope this helps!