<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Validation on Prateek Sharma</title>
		<link>https://prateeksharma.me/tags/validation/</link>
		<description>Recent content in Validation on Prateek Sharma</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 02 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://prateeksharma.me/tags/validation/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Added an e-filing JSON validator to India ITR Copilot</title>
				<link>https://prateeksharma.me/open-source/india-itr-copilot-efiling-validator/</link>
				<pubDate>Sun, 02 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://prateeksharma.me/open-source/india-itr-copilot-efiling-validator/</guid>
				<description>&lt;p&gt;While hand-building a government-schema ITR-3 JSON for AY 2026-27, importing&#xA;it into the tax department&amp;rsquo;s own e-filing utility, and correcting it against&#xA;that utility&amp;rsquo;s re-export, I found several bugs that passed the project&amp;rsquo;s&#xA;existing JSON-schema validation with zero errors the whole time: a&#xA;capital-gains total that gets silently recomputed to zero on import if its&#xA;detail schedule isn&amp;rsquo;t patched alongside it, an exemption that actually&#xA;belongs in a different section than the schema implies, a table that needs&#xA;exact rather than approximate equality with another schedule, a negative&#xA;carry-forward value from a zero-deduction claim, and a contact field left at&#xA;a skeleton default.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
