LWC: Implementing Service Components

A service component is a component that provides an API for a set of functionalities. Ideally, the service should be specialized, generic and reusable. Also, it does not have a markup, i.e. it is not visible by default.

Creating a custom service simplifies component’s code and help reduce code duplication. This in turns makes the code more robust and facilitates maintenance.

To develop a custom service component for my Account object, I have created an accountService component and exposed the below services:

• searchAccount: it accepts a search key and returns the list of accounts matching the key
• getAccounts: this returns a list of 5 accounts

You will notice that I have followed the singleton pattern to define this component, i.e. there can be only one instance of this component. Now to get a reference to these custom services, I have created an accountComponent which is consuming the services like below:

Please see the below repo for the code:
https://github.com/iamsonal/lwc-service

References:
https://developer.salesforce.com/blogs/2018/08/implement-and-use-lightning-service-components.html

LWC: Modularizing Code using Singleton pattern

Imagine that we have a custom LWC component, which we drag-and-drop onto a Lightning page in Lightning App Builder. This component has 2 design attributes for First Name and Last Name. We need a way to access these values from any component without communicating down the containment hierarchy. Setting the public properties of child components becomes a tedious job if there are nested components.

To solve this issue, we can use the Singleton Pattern, which states that the number of instances of an object must be restricted to one only, hence the "single" in Singleton. The intent of the Singleton is ensuring a class has only one instance, and providing a global point of access to it.

For the sake of simplicity, I have created 2 components component1 and component2 where component2 is the child of component1. I need to access the design attribute values of the parent component from the child component. In this example, we are storing the design attribute values in a single central place, sharedData component, written in the Singleton pattern.

which can be accessed by any component in the application like below:

Similarly, to get one point of access to custom labels, I have created a component customLabels using Javascript classes to access the custom labels

To know more about Object.freeze(), refer one of my post titled Javascript: Preventing Object Modification. Now any component in the application can access these values like below:

Please see the below repo for the code:
https://github.com/iamsonal/lwc-singleton

LWC: Modal implementation

Check the code in the below repo for the modal implementation in LWC:
https://github.com/iamsonal/lwc-modal

Notes:

• If you want to hide the close icon, then set the hide-close property to true like below:



<!-- modalContainer.html -->
<template>
    <c-modal name="Modal Name" title="Modal Title" hide-close>
    </c-modal>
</template>

• Similarly, if you want to display a large modal, then set the is-large property to true like below:



<!-- modalContainer.html -->
<template>
    <c-modal name="Modal Name" title="Modal Title" hide-close is-large>
    </c-modal>
</template>




• Using slots (unnamed and named), we are passing the modal body and footer content from parent into the child component like below. In this way, we can control the markup that can be displayed in the modal. For more information about how to use slots, check the LWC documentation.



<c-modal name="Modal Name" title="Modal Title" >

    <!-- Unnamed Slot -->
    <p>This is some content</p>

    <!-- Named Slot -->
    <div slot="footer" style="display: inline;">
        <lightning-button label="Close" variant="neutral" onclick={handleCancelModal}></lightning-button>
    </div>
    
</c-modal>




• Set the style-class property to apply a custom CSS in the modal.