Skip to main content

LWC Code Sample for Weather Component: Building a Dynamic Weather Display

Introduction:

In this blog post, we will explore how to build a Lightning Web Component (LWC) that displays the weather information of a particular location. We will leverage the power of LWC and external APIs to create a dynamic weather display that provides real-time weather data. By the end of this tutorial, you will have a solid understanding of how to integrate APIs and build interactive components using LWC.


Prerequisites:


To follow along with this tutorial, you should have a basic understanding of Lightning Web Components and JavaScript. It's also helpful to have a developer account on Salesforce to leverage its platform and services.


Setting up the Project:


1. Create a new Lightning Web Component by using the Salesforce CLI command:


   sfdx force:lightning:component:create -n WeatherComponent -d force-app/main/default/lwc


2. Navigate to the newly created WeatherComponent directory:


   cd force-app/main/default/lwc/WeatherComponent


3. Open the component in your preferred code editor.


Implementing the Weather Component:

1. Open the WeatherComponent file and replace the default code with the following markup:


   <template>

     <lightning-card title="Weather Information">

       <div class="slds-m-around_medium">

         <lightning-input label="Location" onchange={handleLocationChange}></lightning-input>

         <lightning-button label="Get Weather" onclick={getWeatherData}></lightning-button>

       </div>

       <template if:true={weatherData}>

         <div class="slds-m-around_medium">

           <p>Location: {weatherData.location}</p>

           <p>Temperature: {weatherData.temperature}°C</p>

           <p>Condition: {weatherData.condition}</p>

         </div>

       </template>

     </lightning-card>

   </template>


2. Open the WeatherComponent.js file and replace the default code with the following JavaScript code:


   import { LightningElement, track } from 'lwc';


   export default class WeatherComponent extends LightningElement {

     @track weatherData;

     location;


     handleLocationChange(event) {

       this.location = event.target.value;

     }


     async getWeatherData() {

       const response = await fetch(`https://api.weatherapi.com/v1/current.json?key=YOUR_API_KEY&q=${this.location}`);

       const data = await response.json();

       this.weatherData = {

         location: data.location.name,

         temperature: data.current.temp_c,

         condition: data.current.condition.text,

       };

     }

   }


   Note: Replace YOUR_API_KEY in the API URL with your actual API key. You can obtain a free API key by signing up at weatherapi.com or use any other weather API of your choice.


Explanation:

  1. We define a Lightning Web Component with a card layout, including an input field to enter the location and a button to retrieve the weather data.
  2. On button click, the getWeatherData() method is called, which performs an asynchronous API call to fetch weather information based on the location entered by the user.
  3. The response is then parsed into the weatherData object, which is used to display the location, temperature, and condition of the weather in the component template.

Conclusion:


In this blog post, we explored how to build a dynamic weather display component using Lightning Web Components (LWC). By leveraging external APIs, we were able to fetch real-time weather data and present it in an interactive manner. LWC's flexibility and ease of use make it an excellent choice for creating engaging user interfaces within the Salesforce platform. Feel free to extend this component by adding more features such as additional weather details or styling enhancements. 


Happy coding!

Popular Posts

Must-listen songs for developers

Here are some must-listen songs for developers: "Strobe" by deadmau5 . This electronic dance music (EDM) track is perfect for getting into a flow state. The repetitive beat and simple melody are easy to focus on, and the overall mood of the song is upbeat and motivating.  "Viva la Vida" by Coldplay . This rock song has a soaring melody and powerful lyrics that can inspire you to stay focused and productive. The song's message of hope and resilience is perfect for those times when you're feeling stuck or discouraged.  "Code Monkey" by Jonathan Coulton . This tongue-in-cheek song is a hilarious and accurate portrayal of the life of a software developer. The lyrics are catchy and the song's upbeat tempo will make you want to get up and dance.  "The Sound of Silence" by Simon & Garfunkel . This classic folk song is perfect for those times when you need to focus and concentrate. The song's slow tempo and haunting melody will h...

Uninstall all Windows 10 default apps using Powershell

Here is script to uninstall all windows 10 default modern apps. This script uninstalls xbox, xbox Game bar, Xbox App,Xbox Gaming Overlay, Get started etc from your computer. No need to run one by one commands Just copy below script, run  powershell as administrator and paste script and press enter . It will automatically uninstall all default programs.  If you do not  want to uninstall some apps than just remove " "  line from script. $packages = @( "7EE7776C.LinkedInforWindows" "C27EB4BA.DropboxOEM" "Microsoft.3DBuilder" "Microsoft.Microsoft3DViewer"

Salesforce LWC Code for Multi-Select Lookup

Introduction: In Salesforce Lightning Web Components (LWC), implementing a multi-select lookup field can enhance the user experience and provide greater flexibility for selecting multiple related records. In this blog post, we will walk through the process of creating a multi-select lookup field using LWC. We will cover the required code snippets and provide step-by-step instructions to help you implement this functionality in your Salesforce org.

Apex Test Class Examples for @HttpPost Exposed WebService Class

Introduction: In Salesforce, the Apex programming language allows you to create powerful web services that can be exposed to external systems for data integration. One common scenario is using the @HttpPost annotation to create a custom RESTful web service. In this blog post, we'll walk through some examples of how to write effective test classes for an @HttpPost exposed web service class in Salesforce. Writing comprehensive test classes ensures that your code is robust, functional, and ready for deployment.

Setup vs Non-Setup Objects (Mixed DML)

Core Platform & Fundamentals Module map MODULE 1 root: 'Who can do what, on which objects/fields?' ├─ Setup vs non-setup (transaction rules) ├─ Profile + Perm Sets + PSG (access = union) ├─ Licensing (the ceiling) ├─ CRUD/FLS (objects & fields) └─ Reports/Dashboards (who sees what data) 1.1 Setup vs Non-Setup Objects (Mixed DML) 💬 In plain words:   Salesforce keeps 'admin' records (like User, Group) and 'business' records (like Account, Case) in two separate rooms. One transaction cannot write to both rooms at once — that error is Mixed DML. The fix: do the second write in a separate async step. Concept

How to Save Quote PDF, Send PDF, Preview PDF in salesforce with custom functionality

Want to develop custom pdf viewer, save pdf in quote pdf related List and Send quote to customer on button click when quote is custom in salesforce . These functionality are standard from salesforce. but you can develop these functionality custom in salesforce. Here is the solution:- Custom button to save Quote PDF and send PDF  Step 1:-  First Create Two custom button. which will used for PDF preview and Save quote pdf in quotes pdf related list.                               1. PDF preview Button                              2. Save & Send Quote Button Replace "Your VF page here" to Your quote PDF cuatom page. Step 2:-  PDF preview button   pdf preview button will display the pdf's preview in standard format of salesforce. So you need to set the  following configuration (In picture). After that you have ...

Profiles vs Permission Sets vs Permission Set Groups

Profiles vs Permission Sets vs Permission Set Groups 💬 In plain words:   A Profile is the base uniform every user wears — everyone has exactly one. Permission Sets are extra badges you pin on top for special access. Permission Set Groups are a ready-made bundle of badges. Modern rule: keep the profile minimal, give everything through badges. Concept A Profile is the mandatory 1-per-user baseline (login hours, IP ranges, page-layout assignment, default record types); Permission Sets are additive grants stacked on top; Permission Set Groups (PSGs) bundle permission sets into a user type, with Muting Permission Sets to subtract specific permissions from the bundle without editing its members. Salesforce's stated direction is the 'Minimum Access' profile plus user type-based PSGs — profiles are being progressively drained of permissions (EOL of permissions on profiles has been repeatedly signposted). This underpins Object/Field security (1.4) and interacts with licen...