<?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 Ppanda on Medium]]></title>
        <description><![CDATA[Stories by Ppanda on Medium]]></description>
        <link>https://medium.com/@priyabratapanda.13?source=rss-12e228ccf7eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Ppanda on Medium</title>
            <link>https://medium.com/@priyabratapanda.13?source=rss-12e228ccf7eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:31:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@priyabratapanda.13/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[Virtual DOM & Reconciliation in React]]></title>
            <link>https://medium.com/@priyabratapanda.13/working-of-virtual-dom-in-react-1ad8779fe922?source=rss-12e228ccf7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ad8779fe922</guid>
            <category><![CDATA[reconciliation]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[virtual-dom]]></category>
            <dc:creator><![CDATA[Ppanda]]></dc:creator>
            <pubDate>Sun, 28 Apr 2024 04:02:48 GMT</pubDate>
            <atom:updated>2024-05-04T20:30:37.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*_4r-5aDDYqMdw5VG8q5InA.jpeg" /></figure><h3><strong>Document Object Model (DOM) :</strong></h3><p>The DOM, is a representation of the HTML structure that allows JavaScript to interact with and manipulate the elements on a webpage. Based on the application code, React generates a tree of nodes that describes the app and saved in memory.</p><h4>Problem with Real DOM :</h4><p>DOM manipulation is the heart of any modern web applications. But, it is also a lot slower and very performance heavy. This slowness arises from the fact that most Javascript frameworks used to update the DOM more frequently than needed. To address this problem, the team at Facebook came up with a concept called the <em>virtual DOM.</em></p><h3>Virtual DOM :</h3><p>Virtual DOM is a lightweight and in memory copy of real DOM. When there is a state change, current version of virtual DOM is updated using diffing algorithm. Finally virtual DOM sends batch updates to real DOM to update the user interface(UI).</p><h3><strong>Working of </strong>virtual<strong> DOM :</strong></h3><h4>State Change :</h4><p>Whenever there is a state change (usually via setState) the DOM tree is regenerated and at any given point there are two virtual trees that coexist in memory.</p><h4>Diffing :</h4><p>Next, React compares the two trees and maps out the differences between them and it’ll reconcile those differences. After that, it renders the changes to what we call the Real DOM.</p><h4>Re-render :</h4><p>Finally, it applies the changes to the Real DOM. Also, it has to find the minimum no. of operations necessary to update the Real DOM &amp; then it batches the changes together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*cr6ChzGIhzc0gCK03hVz_A.png" /><figcaption>Visual representation of reconciliation</figcaption></figure><h4>Reconciliation :</h4><p>Finding the minimum no. of modifications required is an O(n³) complexity problem. But React uses an efficient diffing algorithm called <em>heuristic</em> <em>algorithm</em> that reduces time complexity to O(n) to compare two versions of virtual DOM called <em>Reconciliation</em> phase.</p><h3><strong>Conclusion</strong></h3><p>The concept of virtual DOM makes it performance efficient which is one of the unique features of React. <em>Fiber</em> is the new reconciliation engine in React 16 onwards. To know more about fiber please refer : <a href="https://github.com/acdlite/react-fiber-architecture?tab=readme-ov-file#what-is-a-fiber">https://github.com/acdlite/react-fiber-architecture?tab=readme-ov-file#what-is-a-fiber</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ad8779fe922" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Comprehensive Guide to Jutro metadata : If you are transitioning from React]]></title>
            <link>https://medium.com/@priyabratapanda.13/a-beginners-guide-to-guidewire-jutro-digital-platform-23520f1e047b?source=rss-12e228ccf7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/23520f1e047b</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[jutro]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[guide-wire]]></category>
            <category><![CDATA[frontend-development]]></category>
            <dc:creator><![CDATA[Ppanda]]></dc:creator>
            <pubDate>Wed, 06 Mar 2024 22:05:34 GMT</pubDate>
            <atom:updated>2025-02-21T08:59:12.455Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>A Comprehensive Guide to Guidewire Jutro : If you are transitioning from React</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*87J7BBcsJ87POGWARnpsmQ.jpeg" /></figure><p>The Guidewire Jutro Digital Platform (JDP) is an advanced development platform seamlessly integrated with Guidewire’s Cloud Platform and P&amp;C core applications to cater superior user experience (UX). Jutro is a storybook library of components built in React, but specifically tailored to meet the needs of the Digital applications.</p><p>Let’s delve deeper to see which unique feature sets the Jutro Digital Platform apart from any conventional open source library.</p><h3><strong>Building blocks of Jutro components</strong></h3><p>Create a new component directory in the &lt;application&gt;/src/customer folder. In this directory you may create the following files:</p><ul><li><strong><em>ComponentName.metadata.json5</em></strong></li><li><strong><em>ComponentName.jsx</em></strong></li><li><strong><em>ComponentName.message.js</em></strong></li><li><strong><em>ComponentName.module.scss</em></strong></li></ul><h3>Configuration steps of a custom jutro component :</h3><h4>1.Example of a custom(footer) component :</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*JtFmjE_vZsDRodC-JNQAVw.png" /><figcaption>Example code snippet for imports</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*HlgQjGVOtWWEGm-6_zPFug.png" /><figcaption>Example code snippet to validate metadata</figcaption></figure><h4>2.Component Level Override :</h4><p>Override content, property of metadata or message in resolver section will be dynamically replaced at run time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*BwUntZwXGt-weMU1bY68LQ.png" /><figcaption>Example code snippet for override</figcaption></figure><h4>3.Component level Resolvers :</h4><p>The Jutro framework has a mechanism called <em>resolvers</em> to bind static content in UI metadata(JSON) to dynamic content (JavaScript) at run-time. This mechanism bridges the gap between the JSON metadata and the JavaScript code. Jutro provides resolvers for resolving the following: className, callbacks, value, defaultValue etc. All resolvers can be defined as a map or a function. A resolver map provides the simplest way to define design time to run-time mapping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/701/1*OsSR9HGbnawY2FEeW2MwMg.png" /><figcaption>Example code snippet for resolvers</figcaption></figure><h4>4.Rendering custom javaScript components using metadata :</h4><p>Finally override, resolvers and m<em>etadata </em>are passed as arguments to<em> renderContentFromMetadata( ) </em>method.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*fNjVl4B_BLw7R8BgRzXjEQ.png" /><figcaption>Example code snippet</figcaption></figure><h3>UI Metadata schema breakdown :</h3><p>The UI presentation metadata is based on a JSON schema that includes the following types of objects -<em>container, element, field, action</em>, and <em>iterable</em>. You can configure these types and combine them when you are creating your metadata-driven UI. In Digital applications, these objects make up the metadata used to render pages, and screens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*aX5y6VsN3zaUWUa8iaJmZA.png" /></figure><h3><strong>Jutro UI Metadata vs </strong>React Jsx <strong>:</strong></h3><p>It’s important to understand how to write custom metadata to transform the figma wireframe into code using Jutro. In the beginning it might be challenging to understand ui metadata file which is one of the building blocks of jutro platform. Let’s take a simple example and understand how it compares with React component. The below visual representation (UI) could be achieved using both react and Jutro.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*_iqxjtBRtb1EWtjz1K7TFg.png" /></figure><p>React<strong> </strong>Jsx<strong> </strong>Code<strong> </strong>Snippet <strong>(</strong>LHS<strong>) VS </strong>Jutro metadata (RHS) for above visual representation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FLr3h-NPeP5N7vOTuVDCew.png" /></figure><p>As we saw in above example the line of code is significantly higher in Jutro snippet compared to React, it’s important to understand how it’s relatable with the React code snippet as Jutro is built on top of React.</p><h3><strong>React element in depth :</strong></h3><p>Let’s take one step back and start with above example again. Whenever a React component gets called (rendering), under the hood React calls <em>React.createElement()</em> method, which returns the following object :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*J2qaZpnTwDcZaLHoQkRQaw.png" /><figcaption>React Jsx code (LHS) &amp; React.createElement() Object (RHS)</figcaption></figure><p>To further understand this we have to serialize the React code. For our above example code snippet, serialized code looks like following;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0ZGuGBzPCW3uhctcQaIfg.png" /><figcaption>React JSX (LHS) &amp; Serialized Code (RHS)</figcaption></figure><p>The serialized React code generates similar tree structure as the Jutro metadata. following is a visual comparison between serialized React code(LHS) and Jutro metadata(RHS) to create the same visual (UI) representation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7qOCanDV3LrzEhfaDQrQHg.png" /></figure><h3><strong>Conclusion :</strong></h3><p>For Enterprise Engage Applications if you are transitioning from React, this might help to understand the metadata file better however it is not recommended to create metadata(ComponentName.metadata.json5) file for latest version of JDP(Jutro development platform).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23520f1e047b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>