<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Javascript on &lt;shortdiv /&gt;</title>
    <link>https://shortdiv.com/tags/javascript/</link>
    <description>Recent content in Javascript on &lt;shortdiv /&gt;</description>
    <generator>Hugo -- 0.152.0</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 Jun 2018 17:52:37 +0800</lastBuildDate>
    <atom:link href="https://shortdiv.com/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Testing With Custom Matchers in Vue</title>
      <link>https://shortdiv.com/posts/testing-with-custom-matchers/</link>
      <pubDate>Sat, 26 May 2018 15:32:23 -0500</pubDate>
      <guid>https://shortdiv.com/posts/testing-with-custom-matchers/</guid>
      <description>Techniques for writing custom matchers with various popular testing libraries.</description>
    </item>
    <item>
      <title>Old to New; Contexts in React 16.3</title>
      <link>https://shortdiv.com/posts/react-16.3-context-api/</link>
      <pubDate>Sun, 01 Apr 2018 14:18:15 -0500</pubDate>
      <guid>https://shortdiv.com/posts/react-16.3-context-api/</guid>
      <description>&lt;p&gt;A couple of days ago, React 16.3 was released. The update brought with it many changes, including an official (recommended for use) Context API that replaces the old (not recommended for use) Context API, a &lt;code&gt;createRef&lt;/code&gt; API, and a &lt;code&gt;forwardRef&lt;/code&gt; API to name a few. Among the changes introduced in React 16.3, I most anticipated the change to the Context API.&lt;/p&gt;
&lt;h2 id=&#34;adding-context-to-context&#34;&gt;Adding Context to &lt;code&gt;Context&lt;/code&gt;&lt;/h2&gt;
&lt;p&gt;For those of you unfamiliar with the concept, &lt;code&gt;context&lt;/code&gt; is a technique in React used to pass data down from parent to child without having to rely on props. Passing data via props is a common pattern used in React to give children access to parent data. While declarative, passing props can be unnecessarily verbose as it requires passing state explicitly down through the tree. If a child needed access to a grandparent component, the state would have to be passed to every intermediate component regardless of whether or not that component needs access to that data property. React&amp;rsquo;s context feature offers you the ability to pass state down while bypassing intermediary components.&lt;/p&gt;</description>
    </item>
    <item>
      <title>An Ode to Vue</title>
      <link>https://shortdiv.com/posts/an-ode-to-vue/</link>
      <pubDate>Sun, 18 Feb 2018 15:12:39 -0600</pubDate>
      <guid>https://shortdiv.com/posts/an-ode-to-vue/</guid>
      <description>&lt;p&gt;A couple of months ago, I made the switch from React to Vue. I had been playing around with Vue for a bit before making the switch and was impressed by how lightweight, and versatile Vue was. Compared to my initial experience learning React (👋 JSX), picking up Vue felt like a breeze. Not only is Vue very well documented, it is also very straighforward and doesn&amp;rsquo;t require a lot of initial set up to get started. If you&amp;rsquo;ve been considering using Vue in your next project, here are a few of the reasons I think you should use Vue:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
