<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ashan on Medium]]></title>
        <description><![CDATA[Stories by Ashan on Medium]]></description>
        <link>https://medium.com/@ashanrajapaksha954?source=rss-bf85758e3cc3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4WlAaH1jznpbUMkt1fPbEA.png</url>
            <title>Stories by Ashan on Medium</title>
            <link>https://medium.com/@ashanrajapaksha954?source=rss-bf85758e3cc3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:20:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ashanrajapaksha954/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Test React Application with Vitest]]></title>
            <link>https://medium.com/@ashanrajapaksha954/vitest-fefacd62e0e2?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fefacd62e0e2</guid>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Tue, 08 Oct 2024 16:22:32 GMT</pubDate>
            <atom:updated>2024-10-09T01:21:13.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*NL97qZraUqlVrPVMe__N6Q.png" /></figure><p><strong>Introduction</strong><br>When developing React applications, testing is essential to ensure the code’s reliability. Vite is a fast build tool, and Vitest complements it as a testing framework designed specifically for modern front-end development. In this guide, I’ll walk you through setting up Vitest in a Vite React project and demonstrate how to write simple unit tests.</p><p><strong>Setting up a Vite React Project</strong></p><p>Before integrating Vitest, we need to create a Vite React project. If you already have one, you can skip this step.</p><ol><li>Create a new Vite React project:</li></ol><pre>npm create vite@latest my-react-app -- --template react<br>cd my-react-app</pre><p>2. Install the project dependencies:</p><pre>npm install</pre><p><strong>Installing Vitest<br></strong>Once your project is ready, you can add Vitest to start writing and running tests.</p><ol><li><strong>Install Vitest and Testing Library:</strong> Vitest needs to be installed alongside @vitest/ui for UI testing and @testing-library/react for React component testing.</li></ol><pre>npm install vitest @testing-library/react @testing-library/jest-dom</pre><p>2. <strong>Update </strong><strong>vite.config.ts:</strong> Vite doesn’t need significant changes, but we need to add some configuration for Vitest.</p><pre>// vite.config.ts<br>import { defineConfig } from &#39;vite&#39;<br>import react from &#39;@vitejs/plugin-react&#39;<br><br>export default defineConfig({<br>  plugins: [react()],<br>  test: {<br>    environment: &#39;jsdom&#39;, // Simulate the browser for React component testing<br>    globals: true, // To support Jest-like global APIs (like describe, test, etc.)<br>    setupFiles: &#39;./src/setupTests.ts&#39; // Optional: for global setup files<br>  },<br>})</pre><p><strong>Setting up a Test Environment<br></strong>We will now set up our test environment by adding necessary configurations.</p><ol><li>Create a setup file for global configuration:<br>In the root of your src folder (or project root, depending on your structure), create a new file called setupTests.ts. This file will contain the configurations and imports that should run before every test.</li></ol><pre>// src/setupTests.ts<br>import * as matchers from &#39;@testing-library/jest-dom/matchers&#39;;<br>import { expect } from &#39;vitest&#39;;<br><br>expect.extend(matchers);</pre><p>2. Add the test script in package.json:</p><pre>&quot;scripts&quot;: {<br>  &quot;dev&quot;: &quot;vite&quot;,<br>  &quot;build&quot;: &quot;vite build&quot;,<br>  &quot;test&quot;: &quot;vitest&quot;<br>}</pre><p><strong>Writing First Test<br></strong>Let’s write a simple test for a React component to ensure everything is working correctly.</p><ol><li>Create a component:<br>First, create a basic React component that renders some text.</li></ol><pre>// src/components/Hello.tsx<br>const Hello = () =&gt; {<br>  return &lt;h1&gt;Hello, World!&lt;/h1&gt;;<br>};<br>export default Hello;</pre><p>2. Write a test for this component:<br>In the same directory as the Hello.tsx component, create a file named Hello.test.tsx. The .test.tsx extension indicates that this file contains test cases for the component.</p><pre>// src/components/Hello.test.tsx<br>import { render, screen } from &#39;@testing-library/react&#39;<br>import Hello from &#39;./Hello&#39;<br><br>test(&#39;renders the correct text&#39;, () =&gt; {<br>  render(&lt;Hello /&gt;)<br>  expect(screen.getByText(&#39;Hello, World!&#39;)).toBeInTheDocument()<br>})</pre><p>3. <strong>Run the test:</strong> Now, run the test to check if everything is set up correctly.</p><pre>npm run test</pre><p>You should see Vitest running the test and showing the output.</p><p><strong>Running Tests with Vitest UI</strong></p><p>Vitest comes with a user-friendly UI for running and debugging tests. You can enable this UI by running:</p><pre>npm install @vitest/ui<br>npm run test -- --ui</pre><p>This will open a web-based UI where you can view your tests, run them, and debug.</p><p><strong>Conclusion</strong></p><p>Integrating Vitest into a Vite React project is straightforward, offering an efficient testing setup. With Vitest’s fast feedback loop and Vite’s fast build times, you can ensure your React components work as expected without slowing down your development workflow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fefacd62e0e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Static Type Checker — Type Script]]></title>
            <link>https://medium.com/@ashanrajapaksha954/static-type-checker-type-script-a9a9ef879056?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9a9ef879056</guid>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Wed, 27 Mar 2024 02:04:35 GMT</pubDate>
            <atom:updated>2024-03-27T02:04:35.917Z</atom:updated>
            <content:encoded><![CDATA[<h3>Static Type Checker — Type Script</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*SXfBFsbpfPbeX3PvE_gppA.jpeg" /></figure><p>TypeScript offers a powerful feature known as static type checking, which acts as a tool to detect type-related issues before code execution. This feature is invaluable during coding, as it helps identify errors such as</p><ul><li>type mismatches</li><li>undefined variables</li><li>incorrect function parameter</li></ul><p>Let’s look at an example of static type checking in TypeScript:</p><pre>// Define a function that takes two numbers and returns their sum<br>function addNumbers(a: number, b: number): number {<br>    return a + b;<br>}<br><br>// Call the function with correct types<br>const result = addNumbers(5, 10);<br>console.log(result); // Output: 15<br><br>// Call the function with incorrect types (static type checker will catch this)<br>// const errorResult = addNumbers(&#39;5&#39;, 10); // This line will cause a type error</pre><p>One of the key benefits of using static type checking is early error detection. By catching errors at compile time, before code execution, static type checkers reduce the likelihood of runtime errors related to type mismatches, undefined variables, or incorrect function usage.</p><p>In summary, static type checking in TypeScript is a powerful feature that enhances code quality by detecting and preventing type-related issues during development, leading to more robust and reliable software.</p><p>Thank you !✅</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9a9ef879056" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connect to a MongoDB Database Using Node.js with mongoose]]></title>
            <link>https://medium.com/@ashanrajapaksha954/connect-to-a-mongodb-database-using-node-js-with-mongoose-8bb0da6b1114?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bb0da6b1114</guid>
            <category><![CDATA[mongoose]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Tue, 05 Jul 2022 17:06:41 GMT</pubDate>
            <atom:updated>2022-07-05T17:06:41.043Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8CGfFAfG9JAI0JiO2FcBlg.png" /></figure><p>MongoDB is one of the most widely used No-SQL databases in the developer world today. No-SQL databases allow developers to send and retrieve data as JSON documents, instead of SQL objects. To work with MongoDB in a Node.js app, we can use Mongoose.</p><h3>Prerequisites</h3><p>you’ll need to have the following before :</p><ul><li>Node.js installed on your machine.</li><li>A MongoDB instance running on your machine. You won’t need this if you want to use MongoDB Atlas.</li></ul><p><strong>Step 01 , Install mongoose on your node.js environment</strong></p><p>Install Express and Mongoose by executing the following command on a terminal.</p><pre>$ npm install express mongoose --save</pre><p>If you are using Yarn, run:</p><pre>$ yarn add express mongoose</pre><p><strong>Step 02 , Create the connection</strong></p><p>Create a new file server.js to start our Express.js server. Load mongoose and express by adding the following code to server.js.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3164bc8e9b2dcf728ac88901e845d9fa/href">https://medium.com/media/3164bc8e9b2dcf728ac88901e845d9fa/href</a></iframe><p>Then connect to a local MongoDB instance using the mongoose.connect() function.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ff21f06ae49d01c49ca585eaa87e3e0d/href">https://medium.com/media/ff21f06ae49d01c49ca585eaa87e3e0d/href</a></iframe><p>Then, set the app to listen to port 3000.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c63bd2595b8d2760e2705ea83284e56/href">https://medium.com/media/2c63bd2595b8d2760e2705ea83284e56/href</a></iframe><p>This is all about Connect to a MongoDB Database Using Node.js with mongoose….</p><p>Cheers, thanks for reading! 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bb0da6b1114" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Hooks]]></title>
            <link>https://medium.com/@ashanrajapaksha954/react-hooks-8861dfc1f8a5?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/8861dfc1f8a5</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react-hook]]></category>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Tue, 21 Jun 2022 07:19:47 GMT</pubDate>
            <atom:updated>2022-06-21T07:19:47.104Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Ijet6kVJqGgul6adezDLQ.png" /></figure><p><strong>Hooks were added to React in version 16.8. </strong>They let you use state and other React features without writing a class.</p><h4><strong>Why Hooks ???</strong></h4><ul><li><em>Avoid the whole confusion with </em><strong><em>this</em></strong><em> keyword.</em></li><li><em>React features can use without having to write a class.</em></li><li><em>No more method bindings.</em></li><li>Allow you to reuse stateful logic.</li></ul><h4><strong>Basic React Hooks..</strong></h4><p>Basically we used 4 hooks function when we work with react hooks .</p><ul><li><strong>useState() &lt;</strong>state manage&gt;</li><li><strong>useEffect() &lt;</strong>side effect manage&gt;</li><li><strong>useContext() &lt;</strong>context API manage&gt;</li><li><strong>useReducer() &lt;</strong>reducer&gt;</li></ul><h4><strong>useState()</strong></h4><p>This useSate() Hooks allow to <strong>Update</strong> , <strong>handle</strong> and <strong>manipulate</strong> state inside function components without needing to convert in to class component. let’s check with code example below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b05606cb0dcd2d3eaba8485fe12e6b8a/href">https://medium.com/media/b05606cb0dcd2d3eaba8485fe12e6b8a/href</a></iframe><p>To use the <strong>useState</strong> Hook, we first need to <strong>import</strong> it into our component. Like above mentioned code example.</p><p>We initialised our state by using <strong>useState</strong> in our function component. useState accept an initial <strong>state</strong> and returns<strong> two values</strong>.</p><ul><li>The current state</li><li>Function for update state.</li></ul><p>According to above mentioned code example ,<br>The first value <strong>count ,</strong>is the current state.<br>The second value <strong>setCount</strong> , is the function that is used to update our state.</p><p>Lastly, we set the initial state to an 0 value: useState(0)</p><h4>useEffect()</h4><p>React useEffect() is a function that gets executed for 3 different React component lifecycles.<br>Those lifecycles are</p><ul><li>componentDidMount</li><li>componentDidUpdate</li><li>componentWillUnmount</li></ul><p>useEffect runs both after the <strong>first render</strong> <em>and</em> <strong>after every update</strong> . so we can use useEffect in functional component like as above mention lifecycles methods.In below example you can get better understand about using useEffect in react hooks.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9d96c7ab9134b1f6ce0cbf0d89f62e37/href">https://medium.com/media/9d96c7ab9134b1f6ce0cbf0d89f62e37/href</a></iframe><p>We can set the dependency at which change this to fire:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c710fe77e8984f6c53480f7b27c8fadf/href">https://medium.com/media/c710fe77e8984f6c53480f7b27c8fadf/href</a></iframe><p>The above code will only fire once the <strong>count</strong> variable is modified.</p><p>We can also way to run only once on mount , by passing a empty array like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/68d6cf2e8bc437bdef4b13d0d0239aa1/href">https://medium.com/media/68d6cf2e8bc437bdef4b13d0d0239aa1/href</a></iframe><p><strong>Effect Cleanup</strong></p><p>Some effects require cleanup to reduce <strong>memory leaks</strong>.<br><strong>Timeouts, subscriptions, event listeners</strong>, and other effects that are no longer needed should be disposed.<br>We do this by <strong>including a return function</strong> at the end of the useEffect Hook like so.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f6c3ae4391432284e9d932e0c0aaa0cc/href">https://medium.com/media/f6c3ae4391432284e9d932e0c0aaa0cc/href</a></iframe><p><strong>useContext</strong></p><p>In order to use the Context in a child component, we need to access it using the <strong>useContext</strong> Hook.</p><p>First, include the <strong>useContext</strong> in the import statement:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/41745d2c31e8a24a7f5faf7c6882ec33/href">https://medium.com/media/41745d2c31e8a24a7f5faf7c6882ec33/href</a></iframe><p><strong>useReducer</strong></p><p>The <strong>useReducer</strong> Hook is similar to the <strong>useState</strong> Hook.It allows for custom state logic.</p><p>That you can get understand follow below example like so.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4de34a2ae9b0adb5c68b187683d2181d/href">https://medium.com/media/4de34a2ae9b0adb5c68b187683d2181d/href</a></iframe><p>Cheers, thanks for reading! 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8861dfc1f8a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life Cycle Of Angular Components]]></title>
            <link>https://medium.com/@ashanrajapaksha954/life-cycle-of-angular-components-63d2e334df3c?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/63d2e334df3c</guid>
            <category><![CDATA[angularjs]]></category>
            <category><![CDATA[lifecycle-hook]]></category>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Sat, 05 Feb 2022 17:28:57 GMT</pubDate>
            <atom:updated>2022-02-05T17:28:57.965Z</atom:updated>
            <content:encoded><![CDATA[<p>I am going to discuss about life cycle of components. Since in Angular, Component is the main thing in the application, so it is very important for us to understand the life cycle of the components so that we can implement that in our applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*GjZM9-GSHdxM2NuCtf2cyA.png" /></figure><p>In Angular, every component has a life-cycle, a number of different stages it goes through from initialising to destroying. There are 8 different stages in the component lifecycle. Every stage is called life cycle hook events.</p><p>So, we can use these hook events in different phases of our application to obtains fine controls on the components. Since a component is a typescript class, for that reason every component must have a constructor method. The constructor of the component class executes first before the execution of any other life cycle hook event. If we need to inject any dependencies into the component, then the constructor is the best place to inject that dependency. After executing the constructor, Angular executes its life cycle hook methods in a specific order.</p><p>These are the life cycle hook method we have to discuss step by step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*WHI6QVsJO5zIptB7qVHc0w.png" /></figure><p><strong>ngOnChanges</strong></p><p>This one Called when the input properties have changed</p><p><strong>ngOnInit</strong></p><p>This one Called on initialisation the component. This event basically is called only once just after the ngOnChanges() events.</p><p><strong>ngDoCheck</strong></p><p>This event is triggered every time when the input properties of a component are checked.</p><p><strong>ngAfterContentInit</strong></p><p><strong>ngAfterContentInit</strong> is called when the content of a component/directive has initialized. In this case, “content” is the component/directives that are projected in between the &lt;ng-content&gt;&lt;/ng-content&gt; tags. This hook gets call only for once.</p><p><strong>ngAfterContentChecked</strong></p><p>This one fires every cycle of change detection targeting the content DOM . And also this one fires during a component’s initialization stages too. It comes right after ngAfterContentInit.</p><p><strong>ngAfterViewInit</strong></p><p>This lifecycle method gets its call after ngAfterContentChecked and finds its use only on components. This is very much similar to ngAfterContentInit, and it gets invoked only after all the component view and its child view.</p><p><strong>ngAfterViewChecked</strong></p><p>ngAfterViewChecked fires after any change detection cycle targeting the component’s view. The ngAfterViewChecked hook lets developers facilitate how change detection affects the view DOM.</p><p><strong>ngOnDestroy</strong></p><p>ngOnDestroy fires upon a component’s removal from the view and subsequent DOM. This hook provides a chance to clean up any loose ends before a component’s deletion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U6KD5MeVC10ZEL3KMkA6zg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63d2e334df3c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Set Up a React Project with Create React App]]></title>
            <link>https://medium.com/@ashanrajapaksha954/how-to-set-up-a-react-project-with-create-react-app-ffe8ff9b9518?source=rss-bf85758e3cc3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffe8ff9b9518</guid>
            <category><![CDATA[start-react-projecr]]></category>
            <category><![CDATA[create-react-app]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Ashan]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 09:31:00 GMT</pubDate>
            <atom:updated>2020-07-27T16:46:05.341Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*_LslUrocwvsoGbkMPw5D3g.jpeg" /></figure><h3>Introduction</h3><p><a href="https://reactjs.org/">React</a> is a popular JavaScript framework for creating front-end applications. created by Facebook, it has gained popularity by allowing developers to create fast applications using an intuitive programming paradigm that ties JavaScript with an HTML-like syntax known as <a href="https://reactjs.org/docs/introducing-jsx.html">JSX</a>.</p><p><strong>Advantage of React</strong></p><ol><li>Component Reusability</li></ol><p>2. React JS supports React Native JSX</p><p>3. High compilation speed &amp; faster rendering</p><h3>System Setup</h3><p>Before we start a react Project we have check Node.js is already installed or not in your System.. so we can quickly check it executing this command in your command Prompt..</p><p>node --version</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*TuPomqsUqIzUAs6yiOe23A.jpeg" /></figure><p>If not you can go to the Node.js website at <a href="https://nodejs.org/">https://nodejs.org/</a> and download the installer which is needed for your specific operating system.</p><h3>Now Creating A First React Project</h3><p>It’s really simple to create a new app — simply run create-react-app followed by the desired name of your application, and it will scaffold a new app for you. Lets try it out.Now Executing this command in your command Prompt .</p><p>New App Called “my-first-app”</p><pre>npx create-react-app my-first-app</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/671/1*4amKJa2vJPErYZlxLgYsoQ.jpeg" /><figcaption>After create Project show this..</figcaption></figure><p>Then go to your project Executing this command in your command Prompt..</p><p>cd my-first-app</p><p>And from within the project folder start Visual Studio Code via:</p><p>code .</p><p>The project layout should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/303/1*lhMRc9kN8eS3f9YjVb_K2Q.png" /></figure><h3>Now Building &amp; running an application</h3><h4>npm start</h4><p>Inside of your application’s folder, you can run the following commands in your terminal</p><p>npm start</p><p>or</p><p>npm run start</p><p>Runs the app in development mode. Open <a href="http://localhost:3000/">http://localhost:3000</a> to view it in the browser and opened automatically, so that you now should be able to see the following output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eTsVJe9LU0iltWtmwkQtOw.png" /></figure><p>The page will reload if you make edits. You will see the build errors and lint warnings in the console.</p><h3>npm test</h3><p>By default the initial React project comes with some basic unit test cases defined in <em>src/App.test.js</em>. Executing those tests can be done via:</p><p>npm run test</p><p>output can see like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*7AA2jeU6yCe7X1-eRG2D5w.png" /></figure><h3>npm run build</h3><p>Builds the app for production to the build folder.<br> It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes.<br> Your app is ready to be deployed!</p><p>Running the production build is done by using the following command:</p><p>npm run build</p><p>Once the build has been finished successfully you’ll be informed via the following output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/651/1*QA0ZDknYZfGgUtGpk2haqQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffe8ff9b9518" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>