<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Swagger on Pesches Schlauch</title>
    <link>https://pesche.schlau.ch/tags/swagger/</link>
    <description>Recent content in Swagger on Pesches Schlauch</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 01 Dec 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pesche.schlau.ch/tags/swagger/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MicroProfile OpenAPI—Code First</title>
      <link>https://pesche.schlau.ch/2023/12/01/microprofile-openapi-code-first/</link>
      <pubDate>Fri, 01 Dec 2023 00:00:00 +0000</pubDate>
      <guid>https://pesche.schlau.ch/2023/12/01/microprofile-openapi-code-first/</guid>
      <description>&lt;p&gt;You&#39;re given the task of writing a microservice &lt;strong&gt;AND&lt;/strong&gt; providing a documentation&#xA;in OpenAPI format. You already know that there are two main approaches:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;code-first : write the code, using OpenAPI annotations, and then generate the OpenAPI document&lt;/li&gt;&#xA;&lt;li&gt;design-first : write the OpenAPI document (a.k.a. the &lt;code&gt;openapi.yaml&lt;/code&gt; file) and then generate the code&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;This article reviews the code-first approach, the design-first approach will follow&#xA;in a second article at a later time.&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
