<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dotnet-10 on Coding Stephan</title><link>/tags/dotnet-10/</link><description>Recent content in Dotnet-10 on Coding Stephan</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Dec 2025 13:13:15 +0000</lastBuildDate><atom:link href="/tags/dotnet-10/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenAPI in Dotnet 10: Number quirk</title><link>/2025/12/19/openapi-dotnet-10-number-quirk/</link><pubDate>Fri, 19 Dec 2025 13:13:15 +0000</pubDate><guid>/2025/12/19/openapi-dotnet-10-number-quirk/</guid><description>&lt;p&gt;Did you already upgrade your API to Dotnet 10, and are you using OpenAPI specs? Then you might want to read on the next information. We use the &lt;code&gt;Microsoft.AspNetCore.OpenApi&lt;/code&gt; package to generate openapi specifications for our api, which is in turn used to generate client code for various platforms.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m not sure when this started, but it seems numbers are now specified to be either a number or a string with a regex pattern. This causes issues in the generated code and we need it gone.&lt;/p&gt;
&lt;p&gt;Check out the &lt;a href="#update"&gt;update&lt;/a&gt; below if you want to skip the context and go straight to the solution.&lt;/p&gt;</description></item></channel></rss>