Ad
More Related Content
What's hot (20)
Similar to Live Session1 lightning web component (20)
Ad
Recently uploaded (20)
Ad
Live Session1 lightning web component
- 1. FREE WEEKLY LWC SESSION TIMINGS 8PM IST 10:30AM EST 7:30 AM PST
- 2. Smriti Sharan - sfdcAmplified 5X Salesforce Certified Blogger and youtuber at SfdcAmplifed MBA, MS from US Consultant at Deloitte Trailhead Ranger Recognized in top 50 bloggers
- 4. AGENDA What is lightning web component? Difference between aura component and LWC Why do you go for LWC instead of existing aura components? Coexistence and interoperability of aura and LWC
- 5. What is Lightning Web Component ? It Is A New Programming Model To Create The Lightning Components. They Are Custom Html Elements Built Using Html And modern Javascript.
- 6. Advantages of Lightning Web Component BETTER PERFORMANCE MODERN WEB STANDARDS COMPATIBLE WITH AURA COMPONENTS EASE OF USE
- 8. Problems Develop own rendering engine Does support custom element Hard to find workforce Components written in different framework were not interoperable
- 10. LWC Stack
- 12. Benefits of LWC More standard, less proprietary Common Component Model Transferable Skills Easier-to-ramp-up for developers Better Performance
- 13. Aura Vs LWC
- 14. Coexistence and Interoperability AURA COMPONENTS AND LIGHTNING WEB COMPONENTS CAN COEXIST ON THE SAME PAGE AND IN THE SAME RUNTIME . AURA COMPONENTS CAN INCLUDE LIGHTNING WEB COMPONENTS. AURA COMPONENTS AND LIGHTNING WEB COMPONENTS SHARE THE SAME BASE LIGHTNING COMPONENTS.
- 15. Nested composition You can have both Aura components and Lighting web components inside a parent Aura component Lightning web components can only contain other Lightning web components.
- 16. Side-by-side composition Parent Aura component and Parent Lightning web component are not within the same hierarchy but are placed separately in a Lightning App Page.
- 17. What to Choose between Lightning Web Components and Aura Components? Always choose Lightning Web Components unless you need a feature that isn’t supported
- 19. AGENDA STEP 1 : DOWNLOAD AND INSTALL SALESFORCE DX CLI STEP 2 : DOWNLOAD AND INSTALL VSCODE STEP 3 : INSTALL SALESFORCE EXTENSION PACK STEP 4 : CONNECTING WITH YOUR SALESFORCE ORG
- 20. Salesforce CLI A common line interface tool to interact with Salesforce Orgs and manage metadata/data Create and manage orgs Create metadata like Apex Class, Lightning Components Import and Export Data Create and install packages Run apex test Build Automation
- 21. Difference between Salesforce CLI and SFDX Salesforce CLI is a tool Sfdx is an approach to move towards source driven development
- 22. Step 1: Install Salesforce CLI https://developer.salesforce.com/tools/sfdxcli
- 23. Enter sfdx to Ensure CLI is installed
- 24. Step 2:- Install Visual Studio https://code.visualstudio.com/download
- 25. Step 3:- Install Extensions to support Development Salesforce Extension Pack Lightning Web Component
- 27. AGENDA Org Development Model Steps to Setup SalesforceDX (SFDX) for Non Scratch Orgs
- 28. Development Model ORG DEVELOPMENT MODEL PACKAGE DEVELOPMENT
- 29. Step 1: Create Project with Manifest
- 30. Step 2 : Authenticate your org
- 31. Step 3: Retrieve and Deploy Source Deploy Source to Org Retrieve Source from Org
- 33. AGENDA PACKAGE DEVELOPMENT MODEL STEPS TO SETUP SALESFORCEDX (SFDX) FOR SCRATCH ORGS
- 34. Scratch orgs These are orgs consisting of Salesforce code or metadata that can be easily created or destroyed, helping to speed up the standard development workflow.
- 35. Advantages of Scratch orgs Convenient Configurable disposable
- 36. Use Cases of Scratch org Start a new project. Start a new feature branch. Test a new feature. Start automated testing. Perform development tasks directly in an org. Start from “scratch” with a fresh new org
- 37. Points to remember Scratch orgs do not replace sandboxes. Scratch orgs are temporary and they don’t include any production data. Scratch orgs complement Sandboxes. They are great for temporary deployments. use them for peer review and a way to get enhanced test coverage and automation.
- 38. Step 1: Create Project
- 39. Step 2: Authorize Dev hub he Developer Hub (Dev Hub) lets you create and manage scratch orgs.
- 40. Step 3: Enable Dev hub
- 41. Step 4 : Push and pull from Org
- 44. Sfdx Command Structure Command Flag Arguments
- 46. Deploying metadata to a Salesforce instance Step 1: Convert source format to metadata format Step 2: Deploy from scratch to sandbox/ production org Step 3: Check deployment Status
- 47. Overview of Lightning Component Library
- 48. Q&A
- 49. Thank you
Editor's Notes
- #22: Using sfdx we can create scratch orgs –which we will understand in later section
- #23: Salesforce CLI is a single command-line interface that is used in all Salesforce DX features. It reduces development time across the entire Salesforce Platform. Built around open APIs, the CLI easily integrates into existing developer workflows. It can be used to aggregate development tools, synchronize source, manage orgs and data, execute tests, and install packages. CLI is the best interface for interactive command line development, continuous integration, and continuous delivery, and automation. This consolidated interface for many APIs is the driver for Visual Studio Code extensions. It is also the driver of new third-party features like Illuminated Cloud and the Welkin Suite.
- #30: Salesforce CLI is a single command-line interface that is used in all Salesforce DX features. It reduces development time across the entire Salesforce Platform. Built around open APIs, the CLI easily integrates into existing developer workflows. It can be used to aggregate development tools, synchronize source, manage orgs and data, execute tests, and install packages. CLI is the best interface for interactive command line development, continuous integration, and continuous delivery, and automation. This consolidated interface for many APIs is the driver for Visual Studio Code extensions. It is also the driver of new third-party features like Illuminated Cloud and the Welkin Suite.
- #35: We use scratch orgs when working on new requirement or when we start developing new application. When u have build changes then deploy to developer org and delete scratch org.
- #39: Salesforce CLI is a single command-line interface that is used in all Salesforce DX features. It reduces development time across the entire Salesforce Platform. Built around open APIs, the CLI easily integrates into existing developer workflows. It can be used to aggregate development tools, synchronize source, manage orgs and data, execute tests, and install packages. CLI is the best interface for interactive command line development, continuous integration, and continuous delivery, and automation. This consolidated interface for many APIs is the driver for Visual Studio Code extensions. It is also the driver of new third-party features like Illuminated Cloud and the Welkin Suite.
- #40: Salesforce CLI is a single command-line interface that is used in all Salesforce DX features. It reduces development time across the entire Salesforce Platform. Built around open APIs, the CLI easily integrates into existing developer workflows. It can be used to aggregate development tools, synchronize source, manage orgs and data, execute tests, and install packages. CLI is the best interface for interactive command line development, continuous integration, and continuous delivery, and automation. This consolidated interface for many APIs is the driver for Visual Studio Code extensions. It is also the driver of new third-party features like Illuminated Cloud and the Welkin Suite.
- #41: Salesforce CLI is a single command-line interface that is used in all Salesforce DX features. It reduces development time across the entire Salesforce Platform. Built around open APIs, the CLI easily integrates into existing developer workflows. It can be used to aggregate development tools, synchronize source, manage orgs and data, execute tests, and install packages. CLI is the best interface for interactive command line development, continuous integration, and continuous delivery, and automation. This consolidated interface for many APIs is the driver for Visual Studio Code extensions. It is also the driver of new third-party features like Illuminated Cloud and the Welkin Suite.