<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Autosave on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/autosave/</link>
    <description>Recent content in Autosave on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Mar 2023 14:16:04 -0400</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/autosave/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Autosaving with React Hooks</title>
      <link>https://www.bradcypert.com/autosaving-with-react-hooks/</link>
      <pubDate>Sat, 21 Dec 2019 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/autosaving-with-react-hooks/</guid>
      <description>&lt;p&gt;React hooks have really changed the game for me when it comes to building react components. However, I’ve found that writing autosaving functionality is a little less obvious via hooks. Thankfully, it is still possible (and arguably a lot cleaner) when using hooks.&lt;/p&gt;&#xA;&lt;p&gt;We can accomplish autosaving functionality through use of &lt;code&gt;useEffect&lt;/code&gt;. You’ll also need a way to post the data to your server. In my case, I’m using Apollo’s useMutation hook as well. This allows me to post a graphql mutation from a hook-like interface.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
