Close Menu
SalesforceCodex
    Facebook X (Twitter) Instagram
    Trending
    • The Ultimate Guide to Data Cleanup Techniques for Salesforce
    • How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI
    • Top Mistakes Developers Make in Salesforce Apex Triggers
    • Introducing Agentforce3 to Salesforce Developers
    • The Ultimate Guide to Apex Order of Execution for Developers
    • How to Handle Bulkification in Apex with Real-World Use Cases
    • How to Confidently Manage Transactions in Salesforce Apex
    • Building a Dynamic Tree Grid in Lightning Web Component
    Facebook X (Twitter) Instagram
    SalesforceCodex
    Subscribe
    Saturday, August 2
    • Home
    • Salesforce Platform
      • Architecture
      • Apex
      • Lightning Web Components
      • Integration
      • Flows & Automation
      • Best Practices
      • Questions
      • News
      • Books Testimonial
    • Industries
      • Artificial Intelligence
    • Hire Me
    • Certification
      • How to Prepare for Salesforce Integration Architect Exam
      • Certification Coupons
    • Downloads
      • Salesforce Release Notes
      • Apex Coding Guidelines
    • About Us
      • Privacy Policy
    • Contact Us
    SalesforceCodex
    Home»Salesforce»Inheritance in Lightning Web Component

    Inheritance in Lightning Web Component

    Dhanik Lal SahniBy Dhanik Lal SahniApril 11, 2019Updated:April 11, 20196 Comments2 Mins Read
    Facebook Twitter Pinterest LinkedIn Tumblr Email
    Inheritance in Lightning Web Component
    Share
    Facebook Twitter LinkedIn Pinterest Email

    Lightning Web Component is new Salesforce development framework which is based on current Web Standards. We can utilize all features of web standards in our lightning web component. In this blog we will cover one of requirement which is very basic for all lightning community.

    Use Case / Requirement
    We have requirement that, We need to show current user detail on Portal Header. This current user detail can be accessed by other component as well for referring current user information.

    Solution
    As we need to show user detail on other components, so we can create global module or class inheritance. Class Inheritance is important feature of ES6+.

    Let us resolved this task as class inheritance.

    1. Create BaseElement component in your LWC Project.

      import { LightningElement,api } from 'lwc';
      
      export default class BaseElement extends LightningElement {
          @api
          get currentCustomerName() {
              return sessionStorage.getItem("name");
          }
      
          set currentCustomerName(value) {
              sessionStorage.setItem("name",value);
          }
      }
      

      We have used sessionStorage API of window class. This api is used to store information in session, so that value will be accessible in all component in current user session.

    2. Create DerivedElement component in your LWC Project.

      import { track } from 'lwc';
      import BaseElement from 'c/baseElement';
      export default class DerivedElement extends BaseElement {
          //currentCustomerName is declared in base Element
          @track customerName=this.currentCustomerName;
      }
      

      We have inherited derivedElement from BaseElement class. All methods and properties of baseElement will be accessible in derived elements.

    inheritance lightning Lightning web component lwc
    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email
    Previous ArticleImportant facts about Permission Set in Salesforce
    Next Article Salesforce Spring 19 Release Highlights for Admins
    Dhanik Lal Sahni
    • Website

    Related Posts

    By Dhanik Lal Sahni6 Mins Read

    How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI

    July 28, 2025
    By Dhanik Lal Sahni7 Mins Read

    Top Mistakes Developers Make in Salesforce Apex Triggers

    July 25, 2025
    By Dhanik Lal Sahni14 Mins Read

    The Ultimate Guide to Apex Order of Execution for Developers

    July 20, 2025
    View 6 Comments

    6 Comments

    1. Arvind Gautam on April 23, 2019 1:30 pm

      Very nice and concise article to implement this necessary requirement.
      Thanks for your valuable efforts and looking forward for this kind of article in future as well.

      Reply
      • Dhanik Lal Sahni on April 23, 2019 1:33 pm

        Thank You Arvind.

        Reply
    2. Kishan on April 23, 2019 1:30 pm

      such a beautiful post
      it reduce our code
      and give us more flexibility

      Reply
      • Dhanik Lal Sahni on April 23, 2019 1:33 pm

        Thank You Kishan.

        Reply
    3. Dhanik Lal Sahni on May 3, 2020 8:11 am

      Thank You Abhishek. It is great that my blog is useful for ohana.

      Reply
    4. Pingback: Salesforce LWC inheritance and code sharing – Salesforce & MuleSoft Blog

    Leave A Reply Cancel Reply

    Ranked #1 Salesforce Developer Blog by SalesforceBen.com
    SFBenTopDeveloper
    Ranked #4 Salesforce Developer Blog by ApexHours.com
    ApexHoursTopDevelopers
    Categories
    Archives
    Tags
    apex (116) apex best practices (5) apex code best practice (10) apex code optimization (6) Apex logging (4) apex rest (11) apex trigger best practices (6) architecture (22) Asynchronous apex (9) AWS (5) batch apex (10) best code practice (4) code optimization (9) custom metadata types (5) design principle (9) flow (16) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (66) lightning-combobox (5) lightning-datatable (10) lightning component (32) Lightning web component (64) lwc (53) named credential (8) news (4) optimize apex (5) optimize apex code (6) optimize apex trigger (5) Permission set (4) Queueable (9) queueable apex (4) rest api (23) salesforce (150) salesforce apex (52) salesforce api integration (5) Salesforce Interview Question (5) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    MailChimp

    Expert Salesforce Developer and Architect
    Ranked #1 SALESFORCE DEVELOPER BLOG BY SALESFORCEBEN.COM
    Featured on Top Salesforce Developer Blog By ApexHours
    Recent Posts
    • The Ultimate Guide to Data Cleanup Techniques for Salesforce
    • How to Leverage Model Context Protocol (MCP) to Enhance Salesforce AI
    • Top Mistakes Developers Make in Salesforce Apex Triggers
    • Introducing Agentforce3 to Salesforce Developers
    • The Ultimate Guide to Apex Order of Execution for Developers
    Ranked in Top Salesforce Blog by feedspot.com
    RSS Recent Stories
    • Top 10 Salesforce CRM Trends to Watch in 2025 July 18, 2025
    • Discover the Top 10 Salesforce AppExchange Apps to Boost Productivity July 10, 2025
    • Top 20 Salesforce Data Cloud Interview Questions & Answers for Admins June 5, 2025
    • How to Connect Excel to Salesforce to Manage Your Data and Metadata February 9, 2025
    • Difference Between With Security and Without Security in Apex January 2, 2025
    Archives
    Categories
    Tags
    apex (116) apex best practices (5) apex code best practice (10) apex code optimization (6) Apex logging (4) apex rest (11) apex trigger best practices (6) architecture (22) Asynchronous apex (9) AWS (5) batch apex (10) best code practice (4) code optimization (9) custom metadata types (5) design principle (9) flow (16) google (6) google api (4) integration (19) integration architecture (6) lighting (8) lightning (66) lightning-combobox (5) lightning-datatable (10) lightning component (32) Lightning web component (64) lwc (53) named credential (8) news (4) optimize apex (5) optimize apex code (6) optimize apex trigger (5) Permission set (4) Queueable (9) queueable apex (4) rest api (23) salesforce (150) salesforce apex (52) salesforce api integration (5) Salesforce Interview Question (5) salesforce news (5) salesforce question (5) solid (6) tooling api (5) Winter 20 (8)

    Get our newsletter

    Want the latest from our blog straight to your inbox? Chucks us your detail and get mail when new post is published.
    * indicates required

    Facebook X (Twitter) Instagram Pinterest YouTube Tumblr LinkedIn Reddit Telegram
    © 2025 SalesforceCodex.com. Designed by Vagmine Cloud Solution.

    Type above and press Enter to search. Press Esc to cancel.

    Ad Blocker Enabled!
    Ad Blocker Enabled!
    Our website is made possible by displaying online advertisements to our visitors. Please support us by disabling your Ad Blocker.