<?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>WebApi on Software Craftsperson</title>
    <link>https://www.softwarecraftsperson.com/tags/webapi/</link>
    <description>Recent content in WebApi on Software Craftsperson</description>
    <image>
      <title>Software Craftsperson</title>
      <url>https://www.softwarecraftsperson.com/logos/web/png/Color%20logo%20-%20no%20background.png</url>
      <link>https://www.softwarecraftsperson.com/logos/web/png/Color%20logo%20-%20no%20background.png</link>
    </image>
    <generator>Hugo -- 0.147.1</generator>
    <language>en</language>
    <lastBuildDate>Sat, 08 May 2021 15:30:08 +0100</lastBuildDate>
    <atom:link href="https://www.softwarecraftsperson.com/tags/webapi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using ProblemDetails in .NET Core 3.1 with C#</title>
      <link>https://www.softwarecraftsperson.com/posts/2021-05-04-problem-details/</link>
      <pubDate>Sat, 08 May 2021 15:30:08 +0100</pubDate>
      <guid>https://www.softwarecraftsperson.com/posts/2021-05-04-problem-details/</guid>
      <description>Conveying information about an error using ProblemDetails in .NET Core with C#</description>
    </item>
    <item>
      <title>Web API Versioning</title>
      <link>https://www.softwarecraftsperson.com/posts/2021-03-12-web-api-versioning/</link>
      <pubDate>Fri, 12 Mar 2021 22:35:38 +0000</pubDate>
      <guid>https://www.softwarecraftsperson.com/posts/2021-03-12-web-api-versioning/</guid>
      <description>&lt;p&gt;Back-end developers quite often find themselves thinking about making breaking changes to their API. A change that could break the client application consuming the API. We quite often forget how easy it is to cause havoc for our clients by breaking the contract we agreed between front-end and back-end. All sorts of unintentional consequences could arise from this.&lt;/p&gt;
&lt;p&gt;We recently had a similar conversation at my workplace about how we wanted to deal with the release of a feature we had been working on in the last sprint.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
