<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Posts on Tanner Legasse</title>
		<link>https://www.tannerlegasse.com/posts/</link>
		<description>Recent content in Posts on Tanner Legasse</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.tannerlegasse.com/posts/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Leveraging Graphql types in your Shopfiy projects</title>
				<link>https://www.tannerlegasse.com/posts/introspection-and-graphql-types/</link>
				<pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://www.tannerlegasse.com/posts/introspection-and-graphql-types/</guid>
				<description>&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;Software isn&amp;rsquo;t always a clean cut, predictable input to output pipeline. Yes, type systems get us part the way there, but configuring applications to leverage flexible types from an external system is often an underappreciated, important, task. For instance; it&amp;rsquo;s often the case that, when working with external systems, the onus is on us to make sure the data is prepared in a way that&amp;rsquo;s easy to transmit, but the moment we start sending data, we own the relationship between the two systems. Is the data I&amp;rsquo;m providing accurate to types THEY know about? When I&amp;rsquo;m preparing the request payload, how can I ensure that my data is rolling up to something that will be usable? If I&amp;rsquo;m not sure about which data I&amp;rsquo;m querying at runtime, how can I create an internal contract within my software that expresses the relationship accurately?&lt;/p&gt;</description>
			</item>
			<item>
				<title>Manual Shopify App Authentication</title>
				<link>https://www.tannerlegasse.com/posts/manual-shopify-app-authentication/</link>
				<pubDate>Sat, 03 May 2025 00:00:00 +0000</pubDate>
				<guid>https://www.tannerlegasse.com/posts/manual-shopify-app-authentication/</guid>
				<description>&lt;p&gt;Welcome! This is the first of many blog posts covering Shopify application development that will be published here. You&amp;rsquo;ll follow me through the project agnostic portions of app build I&amp;rsquo;m working through. You&amp;rsquo;ll see a production ready app from concept and setup to go-live.&lt;/p&gt;&#xA;&lt;p&gt;If you follow along with this series, you&amp;rsquo;ll see various components take shape, code examples, and a general rundown of why I&amp;rsquo;m making architectural decisions. Here&amp;rsquo;s something I probably don&amp;rsquo;t need to tell you; &lt;strong&gt;I&amp;rsquo;m not perfect. I also don&amp;rsquo;t pretend to be!&lt;/strong&gt; So don&amp;rsquo;t expect brilliant code that stands up against every possible use case and every setting. Expect working code that serves as a foundation for fun experiments, &lt;em&gt;lots&lt;/em&gt; of learning, and real, working apps. In a lot of cases, I&amp;rsquo;ll be encountering problems and matching them to solutions for the first time ever!&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
