<?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 Emmanuel on Medium]]></title>
        <description><![CDATA[Stories by Emmanuel on Medium]]></description>
        <link>https://medium.com/@obapelumi?source=rss-c7c83132e68c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*R5cFT-llHyxsSv-rwtV_OQ.jpeg</url>
            <title>Stories by Emmanuel on Medium</title>
            <link>https://medium.com/@obapelumi?source=rss-c7c83132e68c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:25:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@obapelumi/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[Create a modal window with Vue.js custom directives]]></title>
            <link>https://medium.com/@obapelumi/create-a-modal-window-with-vue-js-custom-directives-d13f7e1b5445?source=rss-c7c83132e68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d13f7e1b5445</guid>
            <category><![CDATA[css-in-js]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[bootstrap]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Emmanuel]]></dc:creator>
            <pubDate>Sun, 11 Aug 2019 19:24:04 GMT</pubDate>
            <atom:updated>2019-08-13T12:19:41.382Z</atom:updated>
            <content:encoded><![CDATA[<p>So I’m that guy that thinks Vue.js can build a spaceship. But let’s build a modal window instead cos it’s way cooler! I had to do this on a project where I couldn’t use bootstrap so I thought to share my solution. We’ll explore Vue.js custom directives and refs to create a solution quite similar to what we are used to with bootstrap modals so let’s get to it!</p><p>First, let’s scaffold our page. I have copied some code from a <a href="http://w3schools.com/">w3schools</a> example on <a href="https://www.w3schools.com/bootstrap/bootstrap_modal.asp">how to create a modal window with bootstrap.js</a> but for this example, we’ll take the bootstrap styles and leave out the js so we can build our own modal from scratch with Vue. You can get the starter code <a href="https://github.com/Obapelumi/Modal-window-with-vuejs-directives/tree/starter">here</a>.</p><p>Bootstrap CSS comes with a few useful styles for modals so we’ll keep most of those. However, we need to override a few things.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e9cdfcc70a1722fc7d91c175cde23712/href">https://medium.com/media/e9cdfcc70a1722fc7d91c175cde23712/href</a></iframe><p>By default the <strong>modal</strong> class has a <strong><em>display: none</em></strong> attribute so we have added a <strong>show </strong>class with <strong><em>display: block. </em></strong>Down the line, we will dynamically add or remove the <strong>show </strong>class to open and close our modal window.</p><p>Now let’s initialize Vue.js and add a data attribute with which to control the <strong>show </strong>class.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4a2869dddd36945d9daa37a33c51c310/href">https://medium.com/media/4a2869dddd36945d9daa37a33c51c310/href</a></iframe><p>Then we bind the show class to the data attribute we’ve created with Vue.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f28a05b30d4ae338c165ba242d3df7ee/href">https://medium.com/media/f28a05b30d4ae338c165ba242d3df7ee/href</a></iframe><p>There are a few ways we can go from here and we could add an @click event to the open and close modal buttons but what if we had several modals on this page? It would be nice to create a separate component for each one with their individual data attributes which we could then manipulate separately. So let’s turn our modal window into a component.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8bcca20daa0518a5cecdc00f8d130e4d/href">https://medium.com/media/8bcca20daa0518a5cecdc00f8d130e4d/href</a></iframe><p>Notice that our component has a slot which allows us the flexibility to put anything we want within our modal. All we need at this point is a way to control when our modal opens or closes. This is where we get to use <strong>refs </strong>and <strong>custom directives</strong>. We will first uniquely identify each modal component using a ref and then take control of them in our directives like so:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/829f48928dfcc9dd1025cd0ab01cf8d0/href">https://medium.com/media/829f48928dfcc9dd1025cd0ab01cf8d0/href</a></iframe><p>Custom directives can have 3 hook functions <strong>bind</strong>,<strong> inserted and update</strong>. Here we use the <strong>bind </strong>hook function to determine what happens when our custom directive gets attached to the element. We passed 3 values into our bind hook function. <strong>el</strong>, <strong>binding </strong>and <strong>vnode</strong>.</p><ol><li><strong>el </strong>represents the element to which the directive is attached. In our bind functions, we are adding an on click event listener to every element our directives get attached to.</li><li><strong>binding</strong> holds whatever values passed into the custom directive. In our case we pass in the <strong>ref</strong> we attached to the modal component we wish to control. We then retrieve this from <strong>binding.value</strong>.</li><li><strong>vnode</strong> is the virtual node produced by Vue’s compiler. It holds the current Vue.js context among other values.</li></ol><p>You can learn more about Vue.js directive hook arguments <a href="https://vuejs.org/v2/guide/custom-directive.html#Directive-Hook-Arguments">here</a>.</p><p>In our directives, we get the current context from <strong>vnode</strong>. We then find the desired modal component from the list of <strong>$refs </strong>that exist on our Vue.js instance using the binding value passed into the directive. This gives us an instance of the referenced v-modal component.</p><p>For <strong>v-modal-open</strong>, we set the show data property to <strong>true</strong> and then we add an <strong>overflowY: hidden </strong>style to the body element to make the modal scrollable. Similarly, for <strong>v-modal-close, </strong>we set the show data property to <strong>false</strong> and then we add an <strong>overflowY: auto </strong>style to the body element to make the rest of the page scrollable when the modal is hidden. Now once we attach our directives to any element they can be used to control any modal on the page by passing in its ref.</p><p>Our solution works very similar to data-toggle and data-target in bootstrap. However, we have leveraged the awesome powers of Vue.js custom directives and it wasn’t that hard! We also get the freedom to give our modals whatever look we want. You could also add your own CSS transitions to make it a little fancier :). Hopefully, you find the ideas here useful. You can find the code for this example <a href="https://github.com/Obapelumi/Modal-window-with-vuejs-directives">here</a> and also a <a href="https://obapelumi.github.io/Modal-window-with-vuejs-directives/">working example</a>. Cheers!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1hueMMAiiTGbGHIN2WzCxg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WOnLrIa21qTcZCDjuMDgWQ.jpeg" /><figcaption>Working Example</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d13f7e1b5445" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Form Validation with HTML & Vuejs]]></title>
            <link>https://itnext.io/form-validation-with-html-vuejs-54ec18e473aa?source=rss-c7c83132e68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/54ec18e473aa</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[form-validation]]></category>
            <dc:creator><![CDATA[Emmanuel]]></dc:creator>
            <pubDate>Sat, 16 Feb 2019 15:42:41 GMT</pubDate>
            <atom:updated>2019-02-23T10:12:07.117Z</atom:updated>
            <content:encoded><![CDATA[<p>They say that most web apps are just HTML forms. Well, forms need validation and thankfully, HTML5 comes with many great in-built form validation capabilities for things like email, numbers, max, min, etc. You can even write your own validation rules with <strong>patterns</strong>. In this article, I will talk about how you can leverage HTML5 validation while overriding the boring defaults, so you can display validation errors as fancy as you like. I will be working with <a href="https://vuejs.org/"><strong>Vuejs</strong></a><strong> </strong>but you can always follow along even if you don’t use Vue.</p><p>Let’s start with a modified version of the Checkout form from <a href="https://getbootstrap.com/docs/4.0/examples/checkout/">bootstrap examples</a> so we don’t have to worry too much about styling. You can clone the starter <a href="https://github.com/Obapelumi/html5-validation-and-vue-starter">here</a>. The setup should look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*lg4K73QpcODX3WmW4Vbnlg.png" /><figcaption>HTML Validation with Vuejs Starter</figcaption></figure><p>The default HTML5 validation doesn’t show all the form errors at once. The irony though is that the browser actually knows all the invalid fields once a user submits, so now all we have to do is check for them and then display however we like.</p><p>Let’s now add an id to our form and a listener that captures the submit event using Vuejs.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/343fe00d32fb7dd6439a3b18812b0934/href">https://medium.com/media/343fe00d32fb7dd6439a3b18812b0934/href</a></iframe><p>Then in our <strong>form-validation.js </strong>file, we will initialize Vuejs and create methods to handle the form submission and validation.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6e16eceae8fde4667233b3c073d44789/href">https://medium.com/media/6e16eceae8fde4667233b3c073d44789/href</a></iframe><p>Here we created 2 methods <strong>submitForm </strong>and <strong>validateForm. submitForm </strong>calls <strong>validateForm </strong>which should return true if all the validation rules are met. For now, we just console log all the invalid form inputs. If we then inspect each one we can find a number of interesting properties including the <strong>validationMessage </strong>which we can display to our users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*GI13v1sKdJqjxkcOeh-J2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*TxjsslwLyTF11GKA-NZtzQ.png" /><figcaption>Invalid input properties</figcaption></figure><p>Next, let’s create the data properties that will hold the <strong>validationErrors </strong>for each of the invalid inputs. Then we will loop through the array of invalid inputs to set each one.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5eacee95f560090d94168e9946ddc90b/href">https://medium.com/media/5eacee95f560090d94168e9946ddc90b/href</a></iframe><p>Here we have done a number of things. We created the <strong>validationErrors </strong>data property to hold the error messages for each field. Each property of the <strong>validationErrors </strong>object corresponds to the name attribute of each form element being validated. So in the <strong>validateForm</strong> method, we clear out any previous error messages and then loop through the invalid fields to set their corresponding validationErrors. We also added an event listener that re-validates once the invalid field has changed.</p><p>Now we need to add name attributes to each field we want to validate, which is quite normal when making forms. Then, of course, we should also add the <strong>span </strong>elements that will display our error messages to the user.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/06a7f163a5e2a61f73acf1d5208813aa/href">https://medium.com/media/06a7f163a5e2a61f73acf1d5208813aa/href</a></iframe><p>Now once we submit the form our users can see all the validation errors they need to fix. What’s cool is that we have done it without having to bring in an extra library just for validation. Now because we’re leveraging Vue’s data binding powers we can really get creative from here on how we want our errors to be displayed.</p><h3>Working with HTML5 Patterns</h3><p>What if we need to extend beyond the available validation rules. For example, checking if a zip code is valid. This is where HTML5 patterns get super useful because we can write regular expressions right in our HTML to perform any kind of checks we need. I feel like someone is swearing at <strong>regular expressions </strong>right now but thankfully you can find a tonne of useful regexes on <a href="http://html5pattern.com/"><strong>html5pattern.com</strong></a>. Right now I haven’t found one for Nigerian zip codes but I know I will.</p><p>Ok, finding a regex was a bit harder than I thought. Turns out they are mostly 7 digit numbers. So <strong>[0–9]{13,16}</strong> should work fine. Now we have a new problem. The error messages on HTML5 patterns are not very helpful so we need to specify our own. We need a way to tell the <strong>validateForm </strong>function what message to display.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d11de43aaaf6401ef238d2136eb46cdb/href">https://medium.com/media/d11de43aaaf6401ef238d2136eb46cdb/href</a></iframe><p>We can then check for the title attribute in the <strong>validateForm </strong>method:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7dc04eea308126d84f0a0d655391f7e5/href">https://medium.com/media/7dc04eea308126d84f0a0d655391f7e5/href</a></iframe><p>Here we added an if-else block that checks for the title attribute and just displays the default error message if it is not found. Also, the <strong>formId </strong>and <strong>errorObjectName </strong>variables are now being passed into the <strong>validateForm </strong>function, this allows us to validate several forms on the same web page how and whenever we choose to.</p><p>We have been able to create a simple convention over configuration method for form validation. Once we specify the name attributes of our form fields in the <strong>validationErrors </strong>object our cool <strong>validateForm </strong>function does the rest by leveraging built-in HTML5 features and all we need to do is display the errors how we want to. As always I hope this helps someone.</p><p>You can use <a href="https://gist.github.com/Obapelumi/113d8a33c3ae4ae412e46de905c3da5a"><strong>this code snippet</strong></a><strong> </strong>to get validation started quickly if you are using Vue and it shouldn’t be that hard to apply to other front-end frameworks as well. You can also find the working code for this article <a href="https://github.com/Obapelumi/HTML5-Validation-and-Vue-Complete"><strong>at</strong> <strong>this repo</strong></a><strong> </strong>and the <a href="https://obapelumi.github.io/HTML5-Validation-and-Vue-Complete/"><strong>demo website here</strong></a>. Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54ec18e473aa" width="1" height="1" alt=""><hr><p><a href="https://itnext.io/form-validation-with-html-vuejs-54ec18e473aa">Form Validation with HTML &amp; Vuejs</a> was originally published in <a href="https://itnext.io/">ITNEXT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pagination With Vuejs]]></title>
            <link>https://medium.com/@obapelumi/pagination-with-vuejs-1f505ce8d15b?source=rss-c7c83132e68c------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f505ce8d15b</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[css]]></category>
            <dc:creator><![CDATA[Emmanuel]]></dc:creator>
            <pubDate>Sat, 02 Jun 2018 12:23:45 GMT</pubDate>
            <atom:updated>2018-06-02T22:36:54.283Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://vuejs.org/"><strong>Vuejs</strong></a> is a simple but powerful framework for developing applications using JavaScript. Trying out Angular and interacting with a few React Applications I often say “Vue can do this, just with less stress”. With the power you get for the easy learning curve, Vue just stands out for me. React and Angular come with a lot more out of the box but if what you want to do is build a truly data-driven JavaScript application Vue is more than enough.</p><p>Now to pagination. While building web applications you will have to deal with presenting data to users based on relevance. So with a blog for example you want to show the most recent posts first. The sorting criteria may differ but you can’t show all the content on one page, so you split it up into pages like a book. Pagination is such a common feature in web applications that I was shocked not to find content about it which was easy to just clone into the app I was building at the time. I had to re-invent the wheel on this one. In this post I will show you how I did it. As we build I will show-off some simple but powerful concepts in <a href="https://vuejs.org/"><strong>Vuejs</strong></a>.</p><p>This post assumes that you know basic <a href="https://vuejs.org/"><strong>Vuejs</strong></a> but you should be able to follow along if you have done some JavaScript in the past. We will be displaying blog posts but we will not be building a back-end for it, thankfully <a href="https://jsonplaceholder.typicode.com/"><strong>JSON placeholder</strong></a> has our back :). <a href="https://jsonplaceholder.typicode.com/"><strong>JSON placeholder</strong></a> is a Fake Online REST API for Testing and Prototyping. We will be getting our blog posts from there and paginating them. To quickly build our page let’s get a nice template from <a href="http://getbootstrap.com/docs/4.1/examples"><strong>Bootstrap Examples</strong></a>. The <a href="http://getbootstrap.com/docs/4.1/examples/album/"><strong>album</strong></a> example template works fine for me. To make this short I have already made changes to the template to fit just right. Clone this <a href="https://github.com/Obapelumi/paginate-with-vue-start"><strong>Git repo</strong></a> and your page should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4utgtv7bDRTUk9-y9Zq0A.png" /><figcaption>paginitation-with-vue-start</figcaption></figure><p>Next, let’s bring in Vue and Axios. Axios is a JavaScript library for sending Http-requests. We will use it to get blog posts from <a href="https://jsonplaceholder.typicode.com/"><strong>JSON placeholder</strong></a>. We also need to create our own <strong>paginate.js</strong> file and link to it. This is where we will write all our Vuejs pagination code. Paste this code at the bottom of your html just before the closing body tag.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6b85fedba764cd64867522efbf359ea0/href">https://medium.com/media/6b85fedba764cd64867522efbf359ea0/href</a></iframe><p>Now to the Vue stuff! We need to tell Vuejs which element in the DOM it should control. For that we add an id attribute to the &lt;main&gt; html tag (I am assuming you cloned the <a href="https://github.com/Obapelumi/paginate-with-vue-start"><strong>Git repo</strong></a><strong> </strong>from earlier). Like so:</p><pre>&lt;main role=&quot;main&quot; id=&quot;pagination-app&quot;&gt;...<br>&lt;/main&gt;</pre><p>Next we initialize our Vue app and define the data variables we need.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2ba478dbd216860d926a921bc16b949/href">https://medium.com/media/b2ba478dbd216860d926a921bc16b949/href</a></iframe><p>The <strong>el </strong>property defines which element our Vue app will control. This will be the <strong>main</strong> html tag to which we added an id of <strong>pagination-app</strong>. The data property contains all the data will be using in our app. <strong>posts </strong>will hold the posts we get from <a href="https://jsonplaceholder.typicode.com/">JSON placeholder</a>. We will be sending our requests to the <strong>baseUrl</strong>. <strong>page </strong>is the current page being viewed, <strong>perPage </strong>defines how many posts we will be viewing per page and <strong>pages </strong>is an array of page numbers which we will populate soon.</p><p>Here’s the idea with this. When we get the posts we will display the first 9, then when a user clicks a page number we will display the posts assigned to that page number. So the first 9 posts are on page 1, the next 9 on page 2 and so on. In the DOM we will then loop through these posts like so;</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6d32ae5bf96ddc6db83a4766667d3c4a/href">https://medium.com/media/6d32ae5bf96ddc6db83a4766667d3c4a/href</a></iframe><p>Notice that we are looping through <strong>displayedPosts </strong>which is a computed property we have not yet declared. Computed properties are really useful when you need to manipulate data before displaying it in the view. We are also looping through the <strong>pages</strong> array to display each page number.</p><p>Now let’s fetch the posts from <a href="https://jsonplaceholder.typicode.com/">JSON placeholder</a> with Axios.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/54740ae77f3f81c8b1293c00e819b02c/href">https://medium.com/media/54740ae77f3f81c8b1293c00e819b02c/href</a></iframe><p>We are using Axios to send a get request to <a href="https://jsonplaceholder.typicode.com/">https://jsonplaceholder.typicode.com/</a>posts . We call the <strong>getPosts</strong> function immediately our page is <strong>created</strong> using the created life-cycle hook <a href="https://vuejs.org/"><strong>Vuejs</strong></a> provides us, then once we get our posts as a response we will set them to the <strong>posts </strong>data property which we defined earlier. <a href="https://jsonplaceholder.typicode.com/">JSON placeholder</a> returns 100 posts so we need to split these up into pages. The number of pages will depend on the number of posts we get back.</p><p>We will now populate the <strong>pages</strong> array with the required page numbers based on the number of posts. To do this we set up something called a <strong>watcher </strong>in <a href="https://vuejs.org/"><strong>Vuejs</strong></a>. Watchers are functions that get run whenever a data property changes. We will be watching the <strong>posts </strong>property so that as it gets set in the <strong>getPosts </strong>method it is used to populate the <strong>pages </strong>array.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49f8ec64d69c621afec32a872e8c5ff4/href">https://medium.com/media/49f8ec64d69c621afec32a872e8c5ff4/href</a></iframe><p>From the <strong>posts</strong> watcher we call the <strong>setPages </strong>method. The for loop in <strong>setPages</strong> populates the <strong>pages</strong> array with numbers from 1 to the number of pages we need to create.</p><p>Now we need a way to decide which posts to show based on the current page number. We will then return these posts in our <strong>displayedPosts </strong>computed property.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2dcc3ec0f954bbad6264846bd3f39341/href">https://medium.com/media/2dcc3ec0f954bbad6264846bd3f39341/href</a></iframe><p>We call the <strong>paginate</strong> method from the <strong>displayedPosts </strong>computed property. Earlier we bound a click event to each page number being displayed<strong>. </strong>The click event sets the <strong>page</strong> data property to the <strong>pageNumber</strong> that was clicked by the user. Because <a href="https://vuejs.org/"><strong>Vuejs</strong></a> is reactive, the <strong>displayedPosts </strong>computed property gets re-evaluated every time the <strong>page </strong>data property changes from a click event.</p><p>The paginate method slices the <strong>posts</strong> array based on the current <strong>page</strong> number and the number of posts <strong>perPage</strong>. So for page 1 it returns posts 0 to 8, for page 2 it returns 9 to 17 and so on. This way we are not directly manipulating the DOM to change the page, we are just changing the data it displays.</p><p>This is a great display of the freedom and elegance <a href="https://vuejs.org/"><strong>Vuejs</strong></a><strong> </strong>can provide. Pagination is one problem that I was able to solve because my Framework got out of the way of flexibility and creative thinking, while offering extremely powerful tools. You can find the complete working code for this post on <a href="https://github.com/Obapelumi/pagination-with-vuejs"><strong>my Git repo</strong></a>. Feel free to tweak it to your own needs. You can also find a working demo <a href="http://demos.obapelumi.dx.am/paginate-with-vue/"><strong>here</strong></a>. Thanks for reading. Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f505ce8d15b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>