<?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>Error-Handling on Blogs by Anil</title>
    <link>https://paudelanil9.com.np/tags/error-handling/</link>
    <description>Recent content in Error-Handling on Blogs by Anil</description>
    <generator>Hugo -- 0.138.0</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://paudelanil9.com.np/tags/error-handling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Layered Error Handling in Go</title>
      <link>https://paudelanil9.com.np/posts/govalidation/</link>
      <pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://paudelanil9.com.np/posts/govalidation/</guid>
      <description>How I went from printing validation errors to a layered error-handling pattern in Go — a stable error vocabulary, a single AppError type, clean validation, one central HTTP handler, and context propagation. Built with Echo and go-playground/validator.</description>
    </item>
  </channel>
</rss>
