Respond to comment

ploeh · Aug 22, 2024 · da71e45 · da71e45
1 parent 6975b15
commit da71e45
Showing 1 changed file with 19 additions and 0 deletions.
diff --git a/_posts/2024-08-12-using-only-a-domain-model-to-persist-restaurant-table-configurations.html b/_posts/2024-08-12-using-only-a-domain-model-to-persist-restaurant-table-configurations.html
@@ -647,4 +647,23 @@ <h2 id="comments-header">
         </div>
         <div class="comment-date">2024-08-19 12:10 UTC</div>
     </div>
+
+    <div class="comment" id="3b2bacb8fa274590ad45cb7864f19848">
+        <div class="comment-author"><a href="/">Mark Seemann</a> <a href="#3b2bacb8fa274590ad45cb7864f19848">#</a></div>
+        <div class="comment-content">
+            <p>
+                Jes, thank you for writing. If by discoverability you mean 'documentation', I would handle that the same way I usually handle documentation requirements for REST APIs: by writing one or my documents that explain how the API works. If there are other possible uses of OpenAPI than that, and the GUI to perform ad-hoc experiments, I'm going to need to be taken to task, because then I'm not aware of them.
+            </p>
+            <p>
+                I've recently discussed <a href="/2024/05/13/gratification">my general misgivings about OpenAPI</a>, and they apply here as well. I'm aware that other people feel differently about this, and that's okay too.
+            </p>
+            <blockquote>
+                "the usual OpenAPI (Swagger et.al.) tools probably takes offence at this type of request object"
+            </blockquote>
+            <p>
+                You may be right, but I haven't tried, so I don't know if this is the case.
+            </p>
+        </div>
+        <div class="comment-date">2024-08-22 16:55 UTC</div>
+    </div>
 </div>